public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "matoro_gcc_bugzilla at matoro dot tk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/112759] New: [13 regression] mips -march=native detection broken with gcc 13+ Date: Wed, 29 Nov 2023 07:10:14 +0000 [thread overview] Message-ID: <bug-112759-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112759 Bug ID: 112759 Summary: [13 regression] mips -march=native detection broken with gcc 13+ Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: driver Assignee: unassigned at gcc dot gnu.org Reporter: matoro_gcc_bugzilla at matoro dot tk Target Milestone: --- Since gcc 13 - and presumably 66c48be23e0fa5ee7474b4b078e013f901c71eed since that is the only recent change to this area - detection of -march=native on mips is broken, defaulting to mips1. With gcc 13: # gcc -march=native -Q --help=target | grep "arch=" | head -n 1 -march=ISA mips1 # gcc --version gcc (Gentoo 13.2.1_p20231014 p9) 13.2.1 20231014 With gcc 12: # gcc -march=native -Q --help=target | grep "arch=" | head -n 1 -march=ISA octeon2 # gcc --version gcc (Gentoo 12.3.1_p20230825 p2) 12.3.1 20230825 Contents of my /proc/cpuinfo are attached. strace seems to indicate that it is reading the data at least: openat(AT_FDCWD, "/proc/cpuinfo", O_RDONLY) = 3 statx(3, "", AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT|AT_EMPTY_PATH, STATX_BASIC_STATS, {stx_mask=STATX_BASIC_STATS|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0444, stx_size=0, ...}) = 0 read(3, "system type\t\t: EBB6800 (CN6880p2"..., 1024) = 1024 close(3) = 0
next reply other threads:[~2023-11-29 7:10 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-29 7:10 matoro_gcc_bugzilla at matoro dot tk [this message] 2023-11-29 7:10 ` [Bug driver/112759] " matoro_gcc_bugzilla at matoro dot tk 2023-11-29 22:16 ` [Bug driver/112759] [13/14 " pinskia at gcc dot gnu.org 2023-11-30 8:42 ` rguenth at gcc dot gnu.org 2023-11-30 15:37 ` matoro_gcc_bugzilla at matoro dot tk 2023-12-13 0:47 ` pinskia at gcc dot gnu.org 2023-12-18 2:24 ` [Bug driver/112759] [13/14 regression] mips -march=native detection broken with gcc 13+ since r13-3178-g66c48be23e0fa5 syq at gcc dot gnu.org 2023-12-18 3:16 ` syq at gcc dot gnu.org 2023-12-23 8:47 ` cvs-commit at gcc dot gnu.org 2023-12-23 8:51 ` cvs-commit at gcc dot gnu.org 2023-12-23 8:55 ` syq 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-112759-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).