https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
Andrew Pinski pinskia at gcc dot gnu.org changed:
What|Removed |Added
CC||amodra at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
--- Comment #19 from Martin Sebor msebor at gcc dot gnu.org ---
Glibc bug #18116 tracks the discussion of the build failure (and the proposed
fix) there:
https://sourceware.org/bugzilla/show_bug.cgi?id=18116
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
Richard Biener rguenth at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |5.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
--- Comment #16 from Michael Meissner meissner at gcc dot gnu.org ---
As I can see there are several issues/whatever.
1) Each of the _ARCH_PWRn is cumulative, so if you say -mcpu=power8 for
instance, it defines _ARCH_PWR4, _ARCH_PWR5,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
Markus Trippelsdorf trippels at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
--- Comment #12 from David Edelsohn dje at gcc dot gnu.org ---
The assembly file should start with
.machine power4
which is the lowest level ISA supported on PPC64 Linux, GLIBC and mtfsf.
If one invokes GCC with multiple -m options, it is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
--- Comment #13 from Markus Trippelsdorf trippels at gcc dot gnu.org ---
It starts with: .machine altivec instead.
But we are talking about powerpc64le-unknown-linux-gnu here.
And -mpower8 is always right in this case, no?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
--- Comment #15 from David Edelsohn dje at gcc dot gnu.org ---
GCC is not magic black box for invoking every other part of the toolchain with
the correct options. If the assembly code uses POWER6 (ISA 2.05) instructions,
it should set the ISA
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
--- Comment #14 from Martin Sebor msebor at gcc dot gnu.org ---
I'm confused: I thought gcc defining the _ARCH_PWR6 macro in response to
-mcpu=power6 or some such implied that the target was power6. Shouldn't gcc
then also invoke the assembler
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
Martin Sebor msebor at gcc dot gnu.org changed:
What|Removed |Added
CC||msebor at gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
--- Comment #7 from David Edelsohn dje at gcc dot gnu.org ---
Was this fixed after Mike's patch? The logic in rs6000_override_options was
ignoring TARGET_DEFAULT.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
--- Comment #3 from Markus Trippelsdorf trippels at gcc dot gnu.org ---
(In reply to David Edelsohn from comment #2)
When did this start? GCC should be passing .machine power8. Was this
before or after Mike's change to processor default?
It
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
--- Comment #5 from Jakub Jelinek jakub at gcc dot gnu.org ---
I think the point is when _ARCH_PWR6 is defined, the assembler should be
already in power6 or later mode (either through .machine directive emitted by
the compiler earlier, or through
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
--- Comment #6 from Martin Sebor msebor at gcc dot gnu.org ---
Ah, yes, I missed that the macro was defined by gcc rather than glibc. It does
look like gcc defines the macro and then invokes as without telling it it's in
power6 mode.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
--- Comment #2 from David Edelsohn dje at gcc dot gnu.org ---
When did this start? GCC should be passing .machine power8. Was this before
or after Mike's change to processor default?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
Jakub Jelinek jakub at gcc dot gnu.org changed:
What|Removed |Added
CC||jakub at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
--- Comment #8 from Martin Sebor msebor at gcc dot gnu.org ---
(In reply to David Edelsohn from comment #7)
I assume the patch you are referring to is r221132 (pr65138). It doesn't look
like that's fixed it. The latest trunk exhibits the same
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
--- Comment #9 from David Edelsohn dje at gcc dot gnu.org ---
GCC is working correctly. The file prologue generated by GCC for a C file now
includes
.machine power8
The example is a pre-processed assembly file. Note the file actively pushes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
--- Comment #10 from Jakub Jelinek jakub at gcc dot gnu.org ---
Ah, indeed, I've totally missed it is a *.S file rather than *.c. Thus this is
certainly a glibc bug, please file it there instead.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
--- Comment #11 from Markus Trippelsdorf trippels at gcc dot gnu.org ---
So one has to use:
CC=gcc -Wa,-mpower8 CXX=g++ -Wa,-mpower8 ../glibc/configure
to configure glibc on ppc64le? This looks odd to me.
Why not pass -mpower8 to the assembler
20 matches
Mail list logo
