public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/95183] [11 Regression] ICE: Segmentation fault (in _cpp_lex_direct)
Date: Mon, 18 May 2020 15:43:05 +0000	[thread overview]
Message-ID: <bug-95183-4-jrbGDzvaau@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95183-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95183

--- Comment #3 from Arseny Solokha <asolokha at gmx dot com> ---
(In reply to Nathan Sidwell from comment #2)
> This is a bug, but you're running a --traditional C preprocessor test
> through the c++ compiler, right?

Through the C compiler, but otherwise yes. I've posted the compiler invocation
in comment 0 verbatim.


> (A regular test run doesn't fail this test
> for me at least)

Yep, because trad.exp adds -traditional-cpp, as intended. But I don't run the
testsuite, but rather use its test cases as part of my larger test corpus,
compiling every individual case in that corpus with randomly chosen compiler
options. IOW, my testing ignores DejaGNU directives in gcc testsuite (which
means it also often ignores common sense when choosing compiler options, as a
consequence).

I can further describe my setup if you are interested, but it's off-topic in
this PR.

  parent reply	other threads:[~2020-05-18 15:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18  5:34 [Bug preprocessor/95183] New: " asolokha at gmx dot com
2020-05-18  6:04 ` [Bug preprocessor/95183] " marxin at gcc dot gnu.org
2020-05-18  6:30 ` rguenth at gcc dot gnu.org
2020-05-18 12:35 ` nathan at gcc dot gnu.org
2020-05-18 14:36 ` nathan at gcc dot gnu.org
2020-05-18 15:43 ` asolokha at gmx dot com [this message]
2020-05-19 13:21 ` nathan at gcc dot gnu.org
2020-05-19 14:01 ` nathan 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-95183-4-jrbGDzvaau@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).