search for: bogden

..., but should never have been added to the GCC aarch64 port at all since there's no compatibility with existing build systems to worry about. I would still like you to show this mythical piece of software that needs this compatibility. -eric On Jan 8, 2014 3:06 AM, "Bernie Ogden" <bogden at arm.com> wrote: > I think there's an error in the example here. > http://gcc.gnu.org/onlinedocs/gcc-4.8.2/gcc/AArch64-Options.html still > documents -mcpu, and that march does not take CPUs as arguments. A local > GCC developer tells me that the documentation is wrong in that...

Thanks Bernie, Feel free to assign yourself to the bug report, just so we know someone is working on it. cheers, -renato On 14 October 2013 17:38, Bernard Ogden <bogden.dev at gmail.com> wrote: > I've got a trivial fix for this problem, and another one which manifests > when thumb is given without an explicit CPU. I'll start pushing it through > our submissions process. > > > On Saturday, 12 October 2013, Renato Golin wrote: > >...

I've got a trivial fix for this problem, and another one which manifests when thumb is given without an explicit CPU. I'll start pushing it through our submissions process. On Saturday, 12 October 2013, Renato Golin wrote: > On 12 October 2013 23:00, Amara Emerson <amara.emerson at gmail.com<javascript:_e({}, 'cvml', 'amara.emerson at gmail.com');> > >

On 12 October 2013 23:00, Amara Emerson <amara.emerson at gmail.com> wrote: > Hi Jan, > > For Cortex-M0, you should probably use the armv6m string in the target > triple. For M3 and M4 you need to use the thumbv7m arch string, -mthumb > won't be necessary. > Yes, but I agree with Jim that a bug must be filled. Jan, would you mind filling a bug?

I think that this works (and adds no appreciable driver complexity) provided that we're not expecting to support -mtune. If clang is (one day) going to be able to isel based on one target and optimize based on another then we might find ourselves wanting to change the meaning of -march from 'isel and optimize' to 'isel only'. So Amara's question about -mtune (or more

...$(CC) -v -dynamiclib $(CFLAG) $^ -o $@ table.o:table.c $(CC) -c $(CFLAG) $^ -o $@ use_table.o:use_table.s $(CC) -c -integrated-as $(CFLAG) $^ -o $@ clean: rm *.o libtest.dylib test //==end Makefile== Cheers, Ashi On Wed, Mar 6, 2013 at 11:59 PM, Bernie Ogden <bogden at arm.com> wrote: > Hi Ashi,**** > > ** ** > > Your first LDR is a pseudoinstruction that is supported by some tools (gas > and armasm, at least), but not by LLVM. Roughly speaking, it turns into a > PC-relative load from a literal pool.**** > > ** ** > > To do...

Hi Ashi, Your first LDR is a pseudoinstruction that is supported by some tools (gas and armasm, at least), but not by LLVM. Roughly speaking, it turns into a PC-relative load from a literal pool. To do what you're trying to achieve you can write your own literal pool in your assembly. You can see some examples of this sort of thing at

Parsing the arch string is a bit icky, but I don't really have too much of a problem with it - and it's better than -mcpu so... -eric On Tue Jan 07 2014 at 9:23:43 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 7 January 2014 17:05, Amara Emerson <amara.emerson at arm.com> wrote: > > We plan on implementing this interface for AArch64 Clang in future, and