public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linux_dr at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105732] New: [REGRESSION] internal compiler error: unspellable token PADDING
Date: Wed, 25 May 2022 22:29:18 +0000	[thread overview]
Message-ID: <bug-105732-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105732
           Summary: [REGRESSION] internal compiler error: unspellable
                    token PADDING
           Product: gcc
           Version: 11.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: linux_dr at yahoo dot com
  Target Milestone: ---

Created attachment 53033
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53033&action=edit
Source file, with no includes, exhibiting the issue.

Regression appeared between 11.2.0 and 11.3.0.

viewable online with "Compiler Explorer”: https://godbolt.org/z/bsenoqdjv

g++ (Compiler-Explorer-Build-gcc--binutils-2.36.1) 11.3.0
Copyright (C) 2021 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.

===What we need===

Please include all of the following items, the first three of which can be
obtained from the output of gcc -v:

* the exact version of GCC:
   + g++ 11.3.0

* the system type:
   + x86_64-linux-gnu

* the options given when GCC was configured/built:
   + From debug output:

COLLECT_GCC=/opt/compiler-explorer/gcc-11.3.0/bin/g++
Target: x86_64-linux-gnu
Configured with: ../gcc-11.3.0/configure
--prefix=/opt/compiler-explorer/gcc-build/staging --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu --disable-bootstrap
--enable-multiarch --with-abi=m64 --with-multilib-list=m32,m64,mx32
--enable-multilib --enable-clocale=gnu
--enable-languages=c,c++,fortran,ada,go,d --enable-ld=yes --enable-gold=yes
--enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-linker-build-id
--enable-lto --enable-plugins --enable-threads=posix
--with-pkgversion=Compiler-Explorer-Build-gcc--binutils-2.36.1
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 11.3.0 (Compiler-Explorer-Build-gcc--binutils-2.36.1)
COLLECT_GCC_OPTIONS='-fdiagnostics-color=always' '-g' '-o' '/app/output.s'
'-masm=intel' '-S' '-v' '-shared-libgcc' '-mtune=generic' '-march=x86-64'
'-dumpdir' '/app/'

* the complete command line that triggers the bug:
   + From debug output:

/opt/compiler-explorer/gcc-11.3.0/bin/../libexec/gcc/x86_64-linux-gnu/11.3.0/cc1plus
-quiet -v -imultiarch x86_64-linux-gnu -iprefix
/opt/compiler-explorer/gcc-11.3.0/bin/../lib/gcc/x86_64-linux-gnu/11.3.0/
-D_GNU_SOURCE <source> -quiet -dumpdir /app/ -dumpbase output.cpp -dumpbase-ext
.cpp -masm=intel -mtune=generic -march=x86-64 -g -version
-fdiagnostics-color=always -o /app/output.s

* the compiler output (error messages, warnings, etc.):
    + (attached)

* the preprocessed file (*.i*) that triggers the bug, generated by adding
-save-temps to the complete compilation command, or, in the case of a bug
report for the GNAT front end, a complete set of source files (see below).
   + As the bug appears to be in the preprocessor, I think the single source
file may be sufficient: (attached)
      (It should also be included in the link above)

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

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25 22:29 linux_dr at yahoo dot com [this message]
2022-05-25 22:30 ` [Bug c++/105732] " linux_dr at yahoo dot com
2022-05-25 22:35 ` linux_dr at yahoo dot com
2022-05-25 22:38 ` pinskia at gcc dot gnu.org
2022-05-25 22:39 ` [Bug preprocessor/105732] [11/12/13 Regression] " pinskia at gcc dot gnu.org
2022-05-25 22:49 ` linux_dr at yahoo dot com
2022-05-25 22:53 ` mpolacek at gcc dot gnu.org
2022-05-25 22:54 ` linux_dr at yahoo dot com
2022-05-25 23:05 ` pinskia at gcc dot gnu.org
2022-05-25 23:06 ` [Bug preprocessor/105732] [9/10/11/12/13 " pinskia at gcc dot gnu.org
2022-05-25 23:44 ` mpolacek at gcc dot gnu.org
2022-05-26 13:38 ` jakub at gcc dot gnu.org
2022-05-26 14:12 ` jakub at gcc dot gnu.org
2022-05-27  6:26 ` rguenth at gcc dot gnu.org
2022-05-27  7:18 ` [Bug preprocessor/105732] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-05-28  6:19 ` herrtimson at yahoo dot de
2022-05-28  6:34 ` jakub at gcc dot gnu.org
2022-05-29 15:13 ` linux_dr at yahoo dot com
2022-05-29 19:58 ` cvs-commit at gcc dot gnu.org
2022-05-30  3:37 ` cvs-commit at gcc dot gnu.org
2022-05-30  7:58 ` [Bug preprocessor/105732] [10/11 " jakub at gcc dot gnu.org
2022-06-10 17:28 ` linux_dr at yahoo dot com
2022-06-10 17:44 ` jakub at gcc dot gnu.org
2022-06-12  2:17 ` linux_dr at yahoo dot com
2022-06-15 12:02 ` cvs-commit at gcc dot gnu.org
2022-06-15 12:06 ` cvs-commit at gcc dot gnu.org
2022-06-15 12:08 ` jakub at gcc dot gnu.org
2023-03-26 15:59 ` jakub 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-105732-4@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).