public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "haochen.jiang at intel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113534] New: printf might report segmentation fault under -mabi=ms Date: Mon, 22 Jan 2024 02:43:53 +0000 [thread overview] Message-ID: <bug-113534-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113534 Bug ID: 113534 Summary: printf might report segmentation fault under -mabi=ms Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: haochen.jiang at intel dot com Target Milestone: --- A reproducer: $ /export/users/haochenj/env/build_no_bootstrap_master/gcc/xgcc -B/export/users/haochenj/env/build_no_bootstrap_master/gcc/ /export/users/haochenj/src/gcc/master/gcc/testsuite/gcc.target/i386/pr80969-4a.c -m64 -DDEBUG -fdiagnostics-plain-output -Ofast -mabi=ms -mavx512f -lm -o ./pr80969-4a.exe $ ./pr80969-4a.exe Segmentation fault (core dumped) After I debug into that, where it core dumped is the "printf ("PASSED\n");" in avx-check.h. We got: Program received signal SIGSEGV, Segmentation fault. 0x00007ffff7db887c in __strlen_evex () from /lib64/libc.so.6 It seems that the seg fault will only happen under -mabi=ms. If we eliminate -mabi=ms, no segmentation fault is detected.
next reply other threads:[~2024-01-22 2:43 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-22 2:43 haochen.jiang at intel dot com [this message] 2024-01-22 2:48 ` [Bug target/113534] " 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-113534-4@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).