public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kranti.rkiran at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/97717] compilation with -O(1/2/3) flag failed while -O0 succeeds Date: Tue, 17 Nov 2020 10:20:41 +0000 [thread overview] Message-ID: <bug-97717-4-LzAutdtdCF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97717-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97717 --- Comment #3 from Rahul Kranti Kiran <kranti.rkiran at gmail dot com> --- The stack size was 8 KB and 'ulimit -s unlimited' worked for root but gets reset as soon as I got back to the userspace. Running the compilation with unlimited stack still threw a SEGFAULT. The complete output of ulimit -a, when running as a root. core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 7823 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 65536 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) unlimited cpu time (seconds, -t) unlimited max user processes (-u) 7823 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited Yes, the compilation was just using -O3 flag. Apologies for the delayed reply.
next prev parent reply other threads:[~2020-11-17 10:20 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-04 17:06 [Bug tree-optimization/97717] New: " kranti.rkiran at gmail dot com 2020-11-04 17:12 ` [Bug tree-optimization/97717] " kranti.rkiran at gmail dot com 2020-11-05 7:38 ` rguenth at gcc dot gnu.org 2020-11-17 10:20 ` kranti.rkiran at gmail dot com [this message] 2021-12-26 6:14 ` pinskia at gcc dot gnu.org 2021-12-26 6:18 ` [Bug middle-end/97717] " pinskia at gcc dot gnu.org 2021-12-26 6:27 ` pinskia at gcc dot gnu.org 2021-12-26 6:37 ` pinskia at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-97717-4-LzAutdtdCF@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).