[Bug inline-asm/62144] "Frame pointer required, but reserved" error with -fomit-frame-pointer but only with -m32 -O2

2018-12-25 Thread coypu at sdf dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62144

coypu  changed:

   What|Removed |Added

 CC||coypu at sdf dot org

--- Comment #10 from coypu  ---
fyi, if you are considering this a bug, I can still reproduce it with trunk as
of gcc (GCC) 9.0.0 20181125

[Bug inline-asm/62144] Frame pointer required, but reserved error with -fomit-frame-pointer but only with -m32 -O2

2014-10-29 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62144

Jakub Jelinek jakub at gcc dot gnu.org changed:

   What|Removed |Added

 CC||jakub at gcc dot gnu.org

--- Comment #7 from Jakub Jelinek jakub at gcc dot gnu.org ---
I'd note that -fomit-frame-pointer is never a guarantee that frame pointer will
be omitted, there are still tons of cases where it can't be omitted, VLAs,
alloca, various specialized builtins, etc.


[Bug inline-asm/62144] Frame pointer required, but reserved error with -fomit-frame-pointer but only with -m32 -O2

2014-10-29 Thread luk32 at o2 dot pl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62144

--- Comment #8 from Łukasz Kucharski luk32 at o2 dot pl ---
Jakub,

fair enough. However, changing the optimization level should not break the
compilation. The issue is, at least for me, is not that we can't omit the frame
pointer, but that it depends on the optimization level.

I couldn't find anything in the docs, which would allow such behaviour. Maybe I
missed it. Anyway, IMO at most a warning should be issued that a potential
optimization conflicts with the flag.

With regards,
luk32.

[Bug inline-asm/62144] Frame pointer required, but reserved error with -fomit-frame-pointer but only with -m32 -O2

2014-10-29 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62144

--- Comment #9 from Jakub Jelinek jakub at gcc dot gnu.org ---
The documentation on -fomit-frame-pointer says: Don't keep the frame pointer
in a register for functions that don't need one.
where whether soemthing needs a frame pointer or not is not precisely defined
(exactly because the actual check in the compiler whether something needs a
frame pointer or not is not really something simple, and depends on many
things).
Whether we can avoid frame pointer on this exact testcase is something Vlad can
perhaps look at, my answer was just general.


[Bug inline-asm/62144] Frame pointer required, but reserved error with -fomit-frame-pointer but only with -m32 -O2

2014-10-28 Thread luk32 at o2 dot pl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62144

Łukasz Kucharski luk32 at o2 dot pl changed:

   What|Removed |Added

 CC||luk32 at o2 dot pl

--- Comment #5 from Łukasz Kucharski luk32 at o2 dot pl ---
Created attachment 33833
  -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=33833action=edit
Example program that fails compilation with optimization enabled.

[Bug inline-asm/62144] Frame pointer required, but reserved error with -fomit-frame-pointer but only with -m32 -O2

2014-10-28 Thread luk32 at o2 dot pl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62144

--- Comment #6 from Łukasz Kucharski luk32 at o2 dot pl ---
Comment on attachment 33833
  -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=33833
Example program that fails compilation with optimization enabled.

Hello, 

I believe we run into the same problem, however we extracted example that
doesn't need `-m32`. Just `-O2` breaks the build. gcc-4.8 passed with no
problems.

With regards,
luk32.

[Bug inline-asm/62144] Frame pointer required, but reserved error with -fomit-frame-pointer but only with -m32 -O2

2014-09-30 Thread vmakarov at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62144

--- Comment #3 from Vladimir Makarov vmakarov at gcc dot gnu.org ---
(In reply to Brooks Moses from comment #2)
 Ping?  Any updates on this?

Sorry, I'll look at this in a week or if I am lucky this week.  Right now, I am
quite busy with register rematerialization pass in LRA which I'd like to make
ready for gcc-5.0.


[Bug inline-asm/62144] Frame pointer required, but reserved error with -fomit-frame-pointer but only with -m32 -O2

2014-09-30 Thread brooks at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62144

--- Comment #4 from Brooks Moses brooks at gcc dot gnu.org ---
Thanks.  I have to admit that that does seem more generally useful!  :)


[Bug inline-asm/62144] Frame pointer required, but reserved error with -fomit-frame-pointer but only with -m32 -O2

2014-09-29 Thread brooks at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62144

--- Comment #2 from Brooks Moses brooks at gcc dot gnu.org ---
Ping?  Any updates on this?


[Bug inline-asm/62144] Frame pointer required, but reserved error with -fomit-frame-pointer but only with -m32 -O2

2014-08-15 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62144

Richard Biener rguenth at gcc dot gnu.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2014-08-15
 CC||vmakarov at gcc dot gnu.org
 Ever confirmed|0   |1

--- Comment #1 from Richard Biener rguenth at gcc dot gnu.org ---
frame_pointer_needed is set by setup_can_eliminate.  Which means that desipte
-fomit-frame-pointer IRA is not able to eliminate the frame pointer?

Vlad?