public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "m+gccbugs at gshep dot ru" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94843] if i use pch and specify '-include' twice compilation fails Date: Wed, 29 Apr 2020 06:58:56 +0000 [thread overview] Message-ID: <bug-94843-4-e8RdCDrXnZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94843-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94843 --- Comment #1 from gccshep <m+gccbugs at gshep dot ru> --- environment: $ uname -a Linux 5user6-7VirtualBox890 5.3.0-46-generic #38~18.04.1-Ubuntu SMP Tue Mar 31 04:17:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux tested with g++-8/9 : $ g++-8 --version g++-8 (Ubuntu 8.4.0-1ubuntu1~18.04) 8.4.0 Copyright (C) 2018 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ g++-9 --version g++-9 (Ubuntu 9.3.0-11ubuntu0~18.04.1) 9.3.0 Copyright (C) 2019 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. It seems like it is reproducible with gcc too. Also reproduced this with gcc/++ 5.5.0 on Slackware 64.
next prev parent reply other threads:[~2020-04-29 6:58 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-29 6:54 [Bug c++/94843] New: " m+gccbugs at gshep dot ru 2020-04-29 6:58 ` m+gccbugs at gshep dot ru [this message] 2020-04-29 7:20 ` [Bug pch/94843] " rguenth 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-94843-4-e8RdCDrXnZ@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).