public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/66903] New: The gcc 4.9.2 crashes when processing declarations such as: int (( ... (x) ... ))
@ 2015-07-17  7:34 speirofr at gmail dot com
  2015-07-17  7:38 ` [Bug c/66903] " speirofr at gmail dot com
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: speirofr at gmail dot com @ 2015-07-17  7:34 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 66903
           Summary: The gcc 4.9.2 crashes when processing declarations
                    such as: int (( ... (x) ... ))
           Product: gcc
           Version: 4.9.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: speirofr at gmail dot com
  Target Milestone: ---

The gcc 4.9.2 crashes when processing declarations such as: int (( ... (x) ...
)), with the number of parens > 4000000.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug c/66903] The gcc 4.9.2 crashes when processing declarations such as: int (( ... (x) ... ))
  2015-07-17  7:34 [Bug c/66903] New: The gcc 4.9.2 crashes when processing declarations such as: int (( ... (x) ... )) speirofr at gmail dot com
@ 2015-07-17  7:38 ` speirofr at gmail dot com
  2015-07-17  9:01 ` speirofr at gmail dot com
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: speirofr at gmail dot com @ 2015-07-17  7:38 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #1 from Salva Peiró <speirofr at gmail dot com> ---
Created attachment 36001
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36001&action=edit
parens.i: Preprocesed sourced with gcc -v -save-temps
>From gcc-bugs-return-492604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 17 08:12:54 2015
Return-Path: <gcc-bugs-return-492604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12490 invoked by alias); 17 Jul 2015 08:12:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12438 invoked by uid 48); 17 Jul 2015 08:12:51 -0000
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/66904] New: cmd/go: "#cgo pkg-config:" comments do not work with gccgo
Date: Fri, 17 Jul 2015 08:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 5.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-66904-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-07/txt/msg01494.txt.bz2
Content-length: 532

https://gcc.gnu.org/bugzilla/show_bug.cgi?idf904

            Bug ID: 66904
           Summary: cmd/go: "#cgo pkg-config:" comments do not work with
                    gccgo
           Product: gcc
           Version: 5.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: go
          Assignee: ian at airs dot com
          Reporter: doko at gcc dot gnu.org
                CC: cmang at google dot com
  Target Milestone: ---

see https://github.com/golang/go/issues/11739


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug c/66903] The gcc 4.9.2 crashes when processing declarations such as: int (( ... (x) ... ))
  2015-07-17  7:34 [Bug c/66903] New: The gcc 4.9.2 crashes when processing declarations such as: int (( ... (x) ... )) speirofr at gmail dot com
  2015-07-17  7:38 ` [Bug c/66903] " speirofr at gmail dot com
@ 2015-07-17  9:01 ` speirofr at gmail dot com
  2015-07-19  3:36 ` pinskia at gcc dot gnu.org
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: speirofr at gmail dot com @ 2015-07-17  9:01 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #2 from Salva Peiró <speirofr at gmail dot com> ---

$ gcc parens.c 
gcc: internal compiler error: Segmentation fault (program cc1)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.9/README.Bugs> for instructions.
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.9/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.9.2-10'
--with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs
--enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.9 --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls
--with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-vtable-verify
--enable-plugin --with-system-zlib --disable-browser-plugin
--enable-java-awt=gtk --enable-gtk-cairo
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/jre --enable-java-home
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-amd64
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar
--enable-objc-gc --enable-multiarch --with-arch-32=i586 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 4.9.2 (Debian 4.9.2-10)
>From gcc-bugs-return-492606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 17 09:04:09 2015
Return-Path: <gcc-bugs-return-492606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108012 invoked by alias); 17 Jul 2015 09:04:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107940 invoked by uid 48); 17 Jul 2015 09:04:00 -0000
From: "miyuki at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/66901] Segmentation fault in compiler instead of error message for ill-formed program with namespace alias and qualified definition
Date: Fri, 17 Jul 2015 09:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: miyuki at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc cf_known_to_fail
Message-ID: <bug-66901-4-rAZmTLnRbZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66901-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66901-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-07/txt/msg01496.txt.bz2
Content-length: 611

https://gcc.gnu.org/bugzilla/show_bug.cgi?idf901

Mikhail Maltsev <miyuki at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ice-on-invalid-code
                 CC|                            |miyuki at gcc dot gnu.org
      Known to fail|                            |6.0

--- Comment #1 from Mikhail Maltsev <miyuki at gcc dot gnu.org> ---
Reproduces on trunk. Possibly a dup of PR66878 (also caused by infinite
recursion in push_inner_scope_r).


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug c/66903] The gcc 4.9.2 crashes when processing declarations such as: int (( ... (x) ... ))
  2015-07-17  7:34 [Bug c/66903] New: The gcc 4.9.2 crashes when processing declarations such as: int (( ... (x) ... )) speirofr at gmail dot com
  2015-07-17  7:38 ` [Bug c/66903] " speirofr at gmail dot com
  2015-07-17  9:01 ` speirofr at gmail dot com
@ 2015-07-19  3:36 ` pinskia at gcc dot gnu.org
  2015-07-19  9:16 ` speirofr at gmail dot com
  2015-07-21 11:08 ` mpolacek at gcc dot gnu.org
  4 siblings, 0 replies; 6+ messages in thread
From: pinskia at gcc dot gnu.org @ 2015-07-19  3:36 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
You are most likely overflowing the stack.  That is the stack is growing and
hitting the stack size.  The default stack size for Linux is 8MB, try using
"ulimit -s unlimited" before running gcc.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug c/66903] The gcc 4.9.2 crashes when processing declarations such as: int (( ... (x) ... ))
  2015-07-17  7:34 [Bug c/66903] New: The gcc 4.9.2 crashes when processing declarations such as: int (( ... (x) ... )) speirofr at gmail dot com
                   ` (2 preceding siblings ...)
  2015-07-19  3:36 ` pinskia at gcc dot gnu.org
@ 2015-07-19  9:16 ` speirofr at gmail dot com
  2015-07-21 11:08 ` mpolacek at gcc dot gnu.org
  4 siblings, 0 replies; 6+ messages in thread
From: speirofr at gmail dot com @ 2015-07-19  9:16 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #4 from Salva Peiró <speirofr at gmail dot com> ---
Confirmed, the cause of the crash is the parser 
_cpp_lex_direct() consuming the default 8 MB Linux stack.

Indeed, ulimit -s shows the stack size limit is set to 8192 KB,
After recompiling with ulimit -s unlimited, the gcc compilation 
succeeds without crashes.

Thanks for the explanation & the time to look at this,
PS: I raised the issue mainly because I was unsure of causes that lead to the
crash.
>From gcc-bugs-return-492771-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 19 11:42:57 2015
Return-Path: <gcc-bugs-return-492771-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59782 invoked by alias); 19 Jul 2015 11:42:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 59743 invoked by uid 48); 19 Jul 2015 11:42:51 -0000
From: "david.abdurachmanov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63304] Aarch64 pc-relative load offset out of range
Date: Sun, 19 Jul 2015 11:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: assemble-failure
X-Bugzilla-Severity: normal
X-Bugzilla-Who: david.abdurachmanov at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-63304-4-Mvxk28oQY8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63304-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63304-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-07/txt/msg01661.txt.bz2
Content-length: 1509

https://gcc.gnu.org/bugzilla/show_bug.cgi?idc304

--- Comment #14 from David Abdurachmanov <david.abdurachmanov at gmail dot com> ---
I hit another two cases of this.

1. g2root tool, which converts GEANT geometry to ROOT geometry. It create a
single function, which contains lots of descriptions of material, shapes, etc.
all describing some 3D objects and physical properties. These can be very huge.

Also could think of MILL computing as possible example. They use C++ as they
assembler (at least for simulation). Thus you have something like:

void somefunc(void) {
  add(b0, b1);
  add(b2, b3);
  ...
}

IIRC, by compiling it they generate a simulator to run this program on specific
CPU.

2. mcfm 6.3 package, to be precise: mcfm-6.3/src/WW/triangle11new.f

triangle11new.s: Assembler messages:
triangle11new.s:587: Error: pc-relative load offset out of range
triangle11new.s:592: Error: pc-relative load offset out of range

..
   587         ldr     x0, .LC2
   588         fmov    d0, x2
   589         fmov    d1, x0
   590         fdiv    d0, d0, d1
   591         fmov    x2, d0
   592         ldr     x0, .LC2
..

346645 .LC2:
346646         .word   0
346647         .word   1073741824
346648         .align  3
..

Distance between ldr instruction and .LC2 is 346058 assembly lines.

Here is the source file:
https://github.com/cms-externals/MCFM/blob/master/src/WW/triangle11new.f (just
1355 sloc).

It's those huge computations, which are killing it. Similar issue as in
OpenLoops package.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug c/66903] The gcc 4.9.2 crashes when processing declarations such as: int (( ... (x) ... ))
  2015-07-17  7:34 [Bug c/66903] New: The gcc 4.9.2 crashes when processing declarations such as: int (( ... (x) ... )) speirofr at gmail dot com
                   ` (3 preceding siblings ...)
  2015-07-19  9:16 ` speirofr at gmail dot com
@ 2015-07-21 11:08 ` mpolacek at gcc dot gnu.org
  4 siblings, 0 replies; 6+ messages in thread
From: mpolacek at gcc dot gnu.org @ 2015-07-21 11:08 UTC (permalink / raw)
  To: gcc-bugs

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |mpolacek at gcc dot gnu.org
         Resolution|---                         |WORKSFORME

--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
I think there's nothing to do for this PR.


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2015-07-21 11:08 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-17  7:34 [Bug c/66903] New: The gcc 4.9.2 crashes when processing declarations such as: int (( ... (x) ... )) speirofr at gmail dot com
2015-07-17  7:38 ` [Bug c/66903] " speirofr at gmail dot com
2015-07-17  9:01 ` speirofr at gmail dot com
2015-07-19  3:36 ` pinskia at gcc dot gnu.org
2015-07-19  9:16 ` speirofr at gmail dot com
2015-07-21 11:08 ` mpolacek at gcc dot gnu.org

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).