[Bug target/41074] Invalid code generation on ARM when using '-fno-omit-frame-pointer' option

siarhei dot siamashka at gmail dot com gcc-bugzilla@gcc.gnu.org
Sat Mar 20 08:46:00 GMT 2010



------- Comment #5 from siarhei dot siamashka at gmail dot com  2010-03-20 08:45 -------
(In reply to comment #4)
> Also, what's the configuration in this case i.e what architecture,
> mode / cpu / fpu ?

Tested on ARM Cortex-A8 hardware, the problematic package built either natively
or crosscompiled, using gcc 4.4.1 without any vendor patches,
'armv4tl-softfloat-linux-gnueabi' was just a build triplet. No other options
were feeded to gcc configure.

> Is there  a smaller testcase which can be looked at ?

As I mentioned in comment 3, the code crashed around the place where it
accesses local variables on stack and where it could not address them directly
(due to immediate offset encoding restrictions), so #4096 deltas were
additionally applied. As such, I'm afraid that reducing this problem to a
smaller testcase may be extremely difficult. I failed to do this so far (I
tried to construct small functions with a huge stack frame exceeding 4K).

> Otherwise this will end up being a WONTFIX bug because we don't have a clear 
> understanding of what / where the failure is.

I had a hope that symptoms description might ring the bell even without a small
testcase provided by me. Or somebody more knowledgeable about gcc internals
could give a hint about what else could be tried to construct such a small
testcase.

I can also try to verify if the crash is still happening with gcc 4.4.3 and
maybe SVN trunk. That's about all I can do at the moment.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41074



More information about the Gcc-bugs mailing list