--- Comment #4 from matz at gcc dot gnu dot org 2009-08-13 15:36 ---
I agree with the reporters. libgcc isn't some random library, GCC should call
it correctly even in the presence of -mregparm.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41055
--- Comment #3 from patrick dot georgi at coresystems dot de 2009-08-13
15:10 ---
(In reply to comment #1)
> -mregparm changes the ABI, you have to rebuild libgcc with -mregparm to be
> able to use it.
>
I agree with that notion for general purpose libraries as used by the user. But
l
--- Comment #2 from stepan at coresystems dot de 2009-08-13 15:08 ---
So we have to rebuild parts of the compiler in order to get a working compiler,
depending on the compiler flags we use? That sounds pretty broken to me. In my
opinion, since -mregparm is a gcc run time option, not a co
--- Comment #1 from rguenth at gcc dot gnu dot org 2009-08-13 14:58 ---
-mregparm changes the ABI, you have to rebuild libgcc with -mregparm to be
able to use it.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
--
