public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "heiko at hexco dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/82469] ICE in _cpp_process_line_notes, at libcpp/lex.c:1066
Date: Wed, 22 Sep 2021 11:00:57 +0000	[thread overview]
Message-ID: <bug-82469-4-WC8X0VDGOI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-82469-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Heiko Eißfeldt <heiko at hexco dot de> ---
I took me a while to find a platform of mine where I got this error.

Right now it happens here as well:

Message:
cpp --traditional -ffreestanding -P gcc_82469.c 
<built-in>: internal compiler error: in _cpp_process_line_notes, at
libcpp/lex.c:1163

OS:
Raspberry Pi, 32-Bit, Linux

uname -a
Linux raspberrypi 5.10.17-v7l+ #1421 SMP Thu May 27 14:00:13 BST 2021 armv7l
GNU/Linux

file /usr/bin/arm-linux-gnueabihf-cpp-8:
/usr/bin/arm-linux-gnueabihf-cpp-8: ELF 32-bit LSB executable, ARM, EABI5
version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for
GNU/Linux 3.2.0, BuildID[sha1]=f4424fc857eedcaef7da81cf953c3ae2788523e7,
stripped

gcc --version
gcc (Raspbian 8.3.0-6+rpi1) 8.3.0

cpp --version
cpp (Raspbian 8.3.0-6+rpi1) 8.3.0

Hardware is a Raspberry Pi Model 4 with 4GB.

Thanks.

  parent reply	other threads:[~2021-09-22 11:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-82469-4@http.gcc.gnu.org/bugzilla/>
2021-09-20 21:39 ` pinskia at gcc dot gnu.org
2021-09-22 11:00 ` heiko at hexco dot de [this message]
2021-10-26  9:26 ` pinskia at gcc dot gnu.org
2021-10-27 17:44 ` acoplan at gcc dot gnu.org
2021-10-28  8:46 ` acoplan 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-82469-4-WC8X0VDGOI@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).