public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.co.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10069: -include switch is improperly handled
Date: Sun, 16 Mar 2003 10:26:00 -0000	[thread overview]
Message-ID: <20030316102601.7574.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/10069; it has been noted by GNATS.

From: Neil Booth <neil@daikokuya.co.uk>
To: Sean McNeil <sean@mcneil.com>
Cc: Steven Bosscher <s.bosscher@student.tudelft.nl>, gcc-gnats@gcc.gnu.org,
	gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org
Subject: Re: c++/10069: -include switch is improperly handled
Date: Sun, 16 Mar 2003 10:19:03 +0000

 Sean McNeil wrote:-
 
 > It would appear that this issue has been addressed somewhere else.  It
 
 Hmm.
 
 > was a bug in how the cc1plus executable handled switches.  That is why I
 > gave the patch to cp/g++spec.c that recognized the switch -include as
 > taking an argument.
 > 
 > I'm not exactly sure how it was addressed.  I'm suspicious that this
 > problem may come back later.  It is peculiar that c++spec.c has to know
 > about switches that take arguments at all.  I'm talking about the check:
 
 If the driver doesn't know what takes arguments, it doesn't know
 reliably where the start and end of a switch is.
 
 > 
 >         else if (((argv[i][2] == '\0'
 >                      && (char *)strchr ("bBVDUoeTuIYmLiA", argv[i][1])
 > != NULL)
 >                     || strcmp (argv[i], "-Xlinker") == 0
 >                     || strcmp (argv[i], "-Tdata") == 0))
 > 
 > Perhaps the cpp initialization now pulls the -include arguments off the
 > list?
 
 If there is a driver problem it hasn't been worked around in cc1plus.
 
 Neil.


             reply	other threads:[~2003-03-16 10:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-16 10:26 Neil Booth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-15 23:56 Sean McNeil
2003-03-15 21:56 Sean McNeil
2003-03-15 21:56 Neil Booth
2003-03-15 21:36 Neil Booth
2003-03-15 21:36 Sean McNeil
2003-03-15 21:26 Neil Booth
2003-03-15 20:26 Sean McNeil
2003-03-15 11:56 Steven Bosscher
2003-03-14  0:06 sean

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=20030316102601.7574.qmail@sources.redhat.com \
    --to=neil@daikokuya.co.uk \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).