public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/105409] ICE in simplify_subreg, at simplify-rtx.cc:7351
Date: Thu, 05 May 2022 13:59:02 +0000 [thread overview]
Message-ID: <bug-105409-4-pItIG2OEvf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105409-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105409
--- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> It seems gm2 omits CC1_SPEC from the cc1/cc1plus invocation in
> gcc/m2/m2-link-support.h.
Indeed: the following trivial patch works wonders indeed:
diff --git a/gcc/m2/m2-link-support.h b/gcc/m2/m2-link-support.h
--- a/gcc/m2/m2-link-support.h
+++ b/gcc/m2/m2-link-support.h
@@ -52,7 +52,7 @@ along with GCC; see the file COPYING3.
compiler. */
#define GM2CC(INPUT,OUTPUT) \
- "%{!fno-exceptions:cc1plus;:cc1} " GM2CC_OPTIONS " " INPUT " \
+ "%{!fno-exceptions:cc1plus;:cc1} %1 " GM2CC_OPTIONS " " INPUT " \
-o %d" SCAFFOLDNAME ".s \n\
" AS(SCAFFOLDNAME ".s",OUTPUT) " "
With it, I get the following test results on sparcv9-sun-solaris2.11:
=== gm2 Summary for unix ===
# of expected passes 11721
# of unexpected failures 7
# of unresolved testcases 1
=== gm2 Summary for unix/-m32 ===
# of expected passes 11706
# of unexpected failures 22
# of unresolved testcases 1
=== gm2 Summary ===
# of expected passes 23427
# of unexpected failures 29
# of unresolved testcases 2
next prev parent reply other threads:[~2022-05-05 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 14:39 [Bug middle-end/105409] New: " ro at gcc dot gnu.org
2022-04-27 14:40 ` [Bug middle-end/105409] " ro at gcc dot gnu.org
2022-05-05 8:24 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-05-05 13:59 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2022-05-05 16:27 ` gaius 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-105409-4-pItIG2OEvf@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).