https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90983
--- Comment #7 from Torsten Robitzki ---
Thanks, that workaround works for me.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90983
--- Comment #5 from Torsten Robitzki ---
(In reply to Martin Sebor from comment #4)
> Using a very large -Wstack-usage argument should effectively disable the
> warning. E.g., -Wstack-usage=4EiB or -Wstack-usage=$(getconf ULONG_MAX).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90983
--- Comment #3 from Torsten Robitzki ---
Is there a workaround to disable that warning (once it was enabled) for the
case, gcc detects an unbound stack usage?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61039
Torsten Robitzki changed:
What|Removed |Added
CC||Torsten at Robitzki dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61427
Torsten Robitzki Torsten at Robitzki dot de changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: Torsten at Robitzki dot de
Hello,
I try to build an arm cross compiler on OSX. The used compiler is gcc version
4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00). After
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61427
--- Comment #1 from Torsten Robitzki Torsten at Robitzki dot de ---
I've tried the same configuration with gcc 4.8.3. The same error occurs in the
config.log, but this time the build stops with:
g++ -I../../libcpp -I. -I../../libcpp/../include
