https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115014
--- Comment #12 from Martin Doucha ---
(In reply to Alexander Monakov from comment #7)
> I think your report was misunderstood. Anyway, when EBP is not a frame
> pointer, I think the chances are low that it is derived from ESP. Would
> accurate
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115014
--- Comment #9 from Martin Doucha ---
(In reply to Andrew Pinski from comment #8)
> Someone in theory could also use an offset from esp and run into a similar
> failure.
Well yes, but that would be an actual stack overflow and the whole point i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115014
--- Comment #6 from Martin Doucha ---
(In reply to Xi Ruoyao from comment #5)
> No, "Freestanding Environment" has a very specific meaning in the C
> standard. If we must add this it'd be a separate -m{something} argument.
I would say that "ex
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115014
--- Comment #4 from Martin Doucha ---
(In reply to Andrew Pinski from comment #3)
> I think most embedded targets use a flat memory system even on x86_64. I
> really think you are barking up the wrong tree on getting this implemented
> in GCC (o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115014
--- Comment #2 from Martin Doucha ---
(In reply to Andrew Pinski from comment #1)
> I am not so sure this is wanted. GCC assumes a flat memory system for stack
> and normal memory accesses .
This is certainly not wanted in the most common case
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115014
Bug ID: 115014
Summary: GCC generates incorrect instructions for addressing
the data segment through EBP register
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
