public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arsen at aarsen dot me" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/108250] [12/13 regression] llvm-tblgen miscompiled on powerpc-unknown-linux-gnu since r12-5383-g22c242342e38eb
Date: Thu, 29 Dec 2022 17:22:10 +0000 [thread overview]
Message-ID: <bug-108250-4-9tQtI4c8Vp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108250-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108250
--- Comment #8 from Arsen Arsenović <arsen at aarsen dot me> ---
Created attachment 54166
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54166&action=edit
xz'd preprocessed CodeGenDagPatterns.cpp
Cmdline: [220/231] /usr/bin/g++-12 -DGTEST_HAS_RTTI=0 -D_FILE_OFFSET_BITS=64
-D_GNU_SOURCE -D_LARGEFILE_SOURCE -D__STDC_CONSTANT_MACROS
-D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
-I/root/llvm-project/bisect-maybe-broken/utils/TableGen
-I/root/llvm-project/llvm/utils/TableGen
-I/root/llvm-project/bisect-maybe-broken/include
-I/root/llvm-project/llvm/include -O2 -mcpu=powerpc -mtune=powerpc -pipe -ggdb
-D_GLIBCXX_ASSERTIONS=1 -fPIC -fno-semantic-interposition
-fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra
-Wno-unused-parameter -Wwrite-strings -Wcast-qual
-Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough
-Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move
-Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor
-Wsuggest-override -Wno-comment -Wno-misleading-indentation
-Wctad-maybe-unsupported -fdiagnostics-color -ffunction-sections
-fdata-sections -O2 -g -DNDEBUG -fno-exceptions -fno-rtti -std=c++17
-save-temps=cwd -MD -MT
utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeGenDAGPatterns.cpp.o -MF
utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeGenDAGPatterns.cpp.o.d -o
utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeGenDAGPatterns.cpp.o -c
/root/llvm-project/llvm/utils/TableGen/CodeGenDAGPatterns.cpp
This is preprocessed by the version with a revert, so the produced assembly
does work, but I have doubts that this matters (copying in the compile from the
bad case and linking against these files still acts like the bad case).
next prev parent reply other threads:[~2022-12-29 17:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 23:35 [Bug c/108250] New: " sam at gentoo dot org
2022-12-28 23:55 ` [Bug c/108250] " sam at gentoo dot org
2022-12-29 0:04 ` sam at gentoo dot org
2022-12-29 0:06 ` sam at gentoo dot org
2022-12-29 2:13 ` [Bug ipa/108250] " pinskia at gcc dot gnu.org
2022-12-29 2:48 ` sam at gentoo dot org
2022-12-29 3:14 ` sam at gentoo dot org
2022-12-29 16:54 ` arsen at aarsen dot me
2022-12-29 17:22 ` arsen at aarsen dot me [this message]
2023-01-02 3:44 ` pinskia at gcc dot gnu.org
2023-01-02 3:46 ` pinskia at gcc dot gnu.org
2023-01-03 1:18 ` sam at gentoo dot org
2023-01-09 14:09 ` rguenth at gcc dot gnu.org
2023-01-13 16:59 ` segher at gcc dot gnu.org
2023-03-27 12:27 ` rguenth at gcc dot gnu.org
2023-05-08 12:26 ` [Bug ipa/108250] [12/13/14 " rguenth at gcc dot gnu.org
2023-05-14 12:06 ` arsen at gcc dot gnu.org
2024-03-28 3:27 ` [Bug ipa/108250] [12/13 " sjames at gcc dot gnu.org
2024-03-28 3:31 ` sjames 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-108250-4-9tQtI4c8Vp@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: link
Be 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).