public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109929] New: profiledbootstrap failure on aarch64-linux-gnu with graphite optimization Date: Mon, 22 May 2023 09:30:14 +0000 [thread overview] Message-ID: <bug-109929-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109929 Bug ID: 109929 Summary: profiledbootstrap failure on aarch64-linux-gnu with graphite optimization Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: xry111 at gcc dot gnu.org Target Milestone: --- Configure GCC trunk with: ../gcc/configure --prefix=$HOME/gcc-trunk --enable-languages=c,c++ --with-system-zlib --disable-fixincludes --disable-werror Note that --disable-werror is needed to work around PR100416. And make it with: make STAGE1_CFLAGS="-O2 -pipe" BOOT_CFLAGS="-O2 -fgraphite-identity -pipe" profiledbootstrap Then some error messages shows up during stagetrain, like: * genhooks: No place specified to document hook TARGET_ASM_OPEN_PAREN * build/genmodes: ../../gcc/gcc/machmode.def:222: no mode "TI" etc. I guess stageprofile compiler is miscompiled, and it miscompiled genhooks and genmodes then. Not sure how to debug the issue.
next reply other threads:[~2023-05-22 9:30 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-22 9:30 xry111 at gcc dot gnu.org [this message] 2023-05-22 9:45 ` [Bug target/109929] " rguenth at gcc dot gnu.org 2023-05-22 10:48 ` xry111 at gcc dot gnu.org 2024-01-19 19:47 ` xry111 at gcc dot gnu.org 2024-01-22 8:52 ` rguenth at gcc dot gnu.org 2024-01-22 9:20 ` xry111 at gcc dot gnu.org 2024-01-22 20:25 ` xry111 at gcc dot gnu.org 2024-01-22 20:57 ` rsandifo 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-109929-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).