llvm dev - Dec 2014 - [LLVMdev] [Compiler-rt] -march=aarch64 flag in gcc/clang

Hi Renato,

Are you sure? Armv8-a is aarch32, not aarch64. Something smells fishy
there.

Cheers,

James
On Thu, 18 Dec 2014 at 08:03, Renato Golin <renato.golin at linaro.org>
wrote:
> On 16 December 2014 at 20:29, Christophe Lyon
> <christophe.lyon at linaro.org> wrote:
> >> I don't see "-march=aarch64" is a valid flag on
either LLVM or GCC.
> >> Should we replace this with a flag which is valid for only aarch64
and
> works for both LLVM and GCC ?
> >
> > I think it should be -march=armv8-a
>
> Sorry folks, that was totally my fault and I was too busy to realise
> it. I have just changed it to "armv8-a" on r224362. I'm
building it
> now and it's working.
>
> cheers,
> --renato
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20141218/92bf2028/attachment.html>

On 18 December 2014 at 09:07, James Molloy <james at jamesmolloy.co.uk>
wrote:
> Hi Renato,
>
> Are you sure? Armv8-a is aarch32, not aarch64. Something smells fishy
there.
>
armv8-a is an architecture.
AArch32 and AArch64 are two different operating modes, both supported
by the armv8-a architecture.
> Cheers,
>
> James
> On Thu, 18 Dec 2014 at 08:03, Renato Golin <renato.golin at
linaro.org> wrote:
>>
>> On 16 December 2014 at 20:29, Christophe Lyon
>> <christophe.lyon at linaro.org> wrote:
>> >> I don't see "-march=aarch64" is a valid flag on
either LLVM or GCC.
>> >> Should we replace this with a flag which is valid for only
aarch64 and
>> >> works for both LLVM and GCC ?
>> >
>> > I think it should be -march=armv8-a
>>
>> Sorry folks, that was totally my fault and I was too busy to realise
>> it. I have just changed it to "armv8-a" on r224362. I'm
building it
>> now and it's working.
>>
>> cheers,
>> --renato
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

Hi,

Right. I'm aware of that. But to Clang, "armv8-a" as an
architecture is
ARMv8/AArch32. Unless Clang has recently got a lot cleverer than it has
been in the past.

James

On Thu Dec 18 2014 at 9:06:04 AM Christophe Lyon <christophe.lyon at
linaro.org>
wrote:
> On 18 December 2014 at 09:07, James Molloy <james at
jamesmolloy.co.uk>
> wrote:
> > Hi Renato,
> >
> > Are you sure? Armv8-a is aarch32, not aarch64. Something smells fishy
> there.
> >
>
> armv8-a is an architecture.
> AArch32 and AArch64 are two different operating modes, both supported
> by the armv8-a architecture.
>
> > Cheers,
> >
> > James
> > On Thu, 18 Dec 2014 at 08:03, Renato Golin <renato.golin at
linaro.org>
> wrote:
> >>
> >> On 16 December 2014 at 20:29, Christophe Lyon
> >> <christophe.lyon at linaro.org> wrote:
> >> >> I don't see "-march=aarch64" is a valid
flag on either LLVM or GCC.
> >> >> Should we replace this with a flag which is valid for
only aarch64
> and
> >> >> works for both LLVM and GCC ?
> >> >
> >> > I think it should be -march=armv8-a
> >>
> >> Sorry folks, that was totally my fault and I was too busy to
realise
> >> it. I have just changed it to "armv8-a" on r224362.
I'm building it
> >> now and it's working.
> >>
> >> cheers,
> >> --renato
> >> _______________________________________________
> >> LLVM Developers mailing list
> >> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20141218/d2084a89/attachment.html>