public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109806] [13/14 Regression] 13.1.0 cc1plus stack smashing crash with C array of complex structs Date: Mon, 15 May 2023 22:35:22 +0000 [thread overview] Message-ID: <bug-109806-4-Ka6zQjFimb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109806-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806 --- Comment #14 from Sam James <sjames at gcc dot gnu.org> --- (In reply to Alexander Monakov from comment #13) > The 128KB stack size is for *secondary* threads on musl (i.e. those created > via pthread_create). The main thread has the same stack as on glibc (GCC > extends it to 128MB unless there's a hard limit). To be fair, I didn't know if gcc did everything in a single thread. Thanks. > > This doesn't look like a stack exhaustion and should be a separate bug. I asked on IRC and was pointed here rather than file a dupe, but I'll file one now in that case.
next prev parent reply other threads:[~2023-05-15 22:35 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-11 2:26 [Bug c++/109806] New: " amy at amyspark dot me 2023-05-11 2:48 ` [Bug tree-optimization/109806] " pinskia at gcc dot gnu.org 2023-05-11 6:46 ` rguenth at gcc dot gnu.org 2023-05-11 9:47 ` amy at amyspark dot me 2023-05-11 9:49 ` amy at amyspark dot me 2023-05-11 12:51 ` rguenth at gcc dot gnu.org 2023-05-11 18:01 ` pinskia at gcc dot gnu.org 2023-05-11 18:56 ` [Bug tree-optimization/109806] [13/14 Regression] " pinskia at gcc dot gnu.org 2023-05-11 20:05 ` jakub at gcc dot gnu.org 2023-05-11 20:44 ` amy at amyspark dot me 2023-05-11 22:45 ` reiter.christoph at gmail dot com 2023-05-12 1:43 ` sjames at gcc dot gnu.org 2023-05-15 21:35 ` sjames at gcc dot gnu.org 2023-05-15 22:27 ` amonakov at gcc dot gnu.org 2023-05-15 22:35 ` sjames at gcc dot gnu.org [this message] 2023-05-15 22:41 ` jakub at gcc dot gnu.org 2023-05-15 22:49 ` sjames at gcc dot gnu.org 2023-07-27 9:26 ` rguenth at gcc dot gnu.org 2024-01-12 11:30 ` rguenth at gcc dot gnu.org 2024-01-12 21:12 ` amy at amyspark dot me 2024-01-13 2:23 ` amy at amyspark dot me
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-109806-4-Ka6zQjFimb@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).