[llvm] r200051 - [Mips] TargetStreamer ELF flag Support for default and commandline options.

Daniel Sanders Daniel.Sanders at imgtec.com
Wed Jan 29 03:44:25 PST 2014


> -----Original Message-----
> From: Rafael EspĂ­ndola [mailto:rafael.espindola at gmail.com]
> Sent: 28 January 2014 15:07
> To: Daniel Sanders
> Cc: Jack Carter; llvm-commits
> Subject: Re: [llvm] r200051 - [Mips] TargetStreamer ELF flag Support for
> default and commandline options.
> 
> On 28 January 2014 06:08, Daniel Sanders <Daniel.Sanders at imgtec.com>
> wrote:
> > Almost all of that makes sense to me. Thanks. The one bit that didn't make
> sense to me is below.
> >
> >> Please note that from the MC point of view, all that you need to be
> >> able to parse are the directives that the mips codegen produces. You
> >> don't even need to be able to parse any real instructions (nop will do).
> >
> > I'm surprised by the last sentence in particular. Surely the MC layer needs
> to be able to parse the instructions in codegens output for the same reason it
> needs to be able to parse the directives emitted by codegen. Partly to avoid
> assembly output being an unreliable debugging tool, and partly to be able to
> assemble to a desired object file.
> 
> To have a full assembler, yes. To be able to test the changes in question, no.
> All the changes being discussed only alter which flags are set in a symbol or
> file header. To test those it only need to be able to handle directives, labels
> and nops.

Ok that makes sense then. I thought we were talking about the MC layer in general.




More information about the llvm-commits mailing list