public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "estellnb at elstel dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105293] g++-8/i586: internal compiler error trying to compile with g++ (evtl. related to qt5/moc bug) Date: Mon, 18 Apr 2022 17:38:11 +0000 [thread overview] Message-ID: <bug-105293-4-N2wMUOIgnt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105293-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105293 --- Comment #5 from Elmar Stellnberger <estellnb at elstel dot org> --- Created attachment 52827 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52827&action=edit 2nd version of patch that should be useable under gcc-8-8.3.0/debian/patches/ Last time I reported that I could not test the patch posted here because the result of package creation with dpkg-buildpackage had vanished. Luckily I found gcc/xg++ and gcc/xgcc which were the required executables that could be installed into /bin/ and tested whether they compiled the new Firefox. g++ with the last patch did not do this. Consequently I have checked out 10.2.2, newer than the last known working good one (10.1.1) from Debian 11 and analysed all changes along the backtrace again. What I found is condensed in the patch above: discover_nonconstant_array_refs (); - was moved up in addition to the other change tested already before If the error is evoked by what is called along the backtrace this needs to resolve it. (I assume now that the Qt5/moc bug is independent and do not use it as reference for the gcc version to compare against any more). Otherwise, the error may stem from something done in a previous pass: during RTL pass: expand Unfortunately this time I was not even able to compile gcc/xg++. Makefiles were garbled, xgcc did not produce a.out (test in Makefile), texinfo files were invalid and I had to copy them from a fresh root and ultimately xg++ stayed the same after all. I had rescued the original g++ as /bin/g++ and that one turned into a link (I know it was a regular file before) although all debian/rules Makefiles only ship into debian/tmp/usr/... and not /. Absolutely no chance to test this second patch! Perhaps someone else can do.
next prev parent reply other threads:[~2022-04-18 17:38 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-16 18:31 [Bug c++/105293] New: " estellnb at elstel dot org 2022-04-16 18:56 ` [Bug c++/105293] " estellnb at elstel dot org 2022-04-17 9:35 ` estellnb at elstel dot org 2022-04-17 15:13 ` estellnb at elstel dot org 2022-04-17 18:31 ` estellnb at elstel dot org 2022-04-18 17:38 ` estellnb at elstel dot org [this message] 2022-04-19 9:25 ` rguenth at gcc dot gnu.org 2024-04-13 1:17 ` 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-105293-4-N2wMUOIgnt@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).