public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Gaius Mulley <gaius@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/modula-2] PR-105409 Bugfix add CC1_SPEC to the cc1/cc1plus invocation.
Date: Thu,  5 May 2022 16:25:40 +0000 (GMT)	[thread overview]
Message-ID: <20220505162540.3DC0B3858D3C@sourceware.org> (raw)

https://gcc.gnu.org/g:ae56a3ce252147379dbfd13e250f728e6504ae2b

commit ae56a3ce252147379dbfd13e250f728e6504ae2b
Author: Gaius Mulley <gaius.mulley@southwales.ac.uk>
Date:   Thu May 5 17:23:03 2022 +0100

    PR-105409 Bugfix add CC1_SPEC to the cc1/cc1plus invocation.
    
    Introducing patch devised by Rainer Orth <ro@CeBiTec.Uni-Bielefeld.de>.
    The lack of CC1_SPEC options to cc1plus can cause an ICE.
    
    gcc/m2/ChangeLog:
    
            * m2-link-support.h (GM2CC): Add CC1_SPEC to the cc1/cc1plus
            invocation.
    
    Signed-off-by: Gaius Mulley <gaius.mulley@southwales.ac.uk>

Diff:
---
 gcc/m2/m2-link-support.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/m2/m2-link-support.h b/gcc/m2/m2-link-support.h
index 66a444edbe7..22325968e25 100644
--- a/gcc/m2/m2-link-support.h
+++ b/gcc/m2/m2-link-support.h
@@ -56,7 +56,7 @@ along with GCC; see the file COPYING3.  If not see
    compiler.  */
 
 #define GM2CC(INPUT,OUTPUT) \
-  "%{!fno-exceptions:cc1plus;:cc1} " GM2CC_OPTIONS " " INPUT " \
+  "%{!fno-exceptions:cc1plus;:cc1} %1" GM2CC_OPTIONS " " INPUT " \
      -o " RM_IF_NOSAVETEMP SCAFFOLDNAME ".s \n\
   " AS(SCAFFOLDNAME ".s",OUTPUT) " "


                 reply	other threads:[~2022-05-05 16:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220505162540.3DC0B3858D3C@sourceware.org \
    --to=gaius@gcc.gnu.org \
    --cc=gcc-cvs@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).