[Bug other/116744] RFE: can generated SARIF file be a container for "everything" needed for a bug-report against gcc?

2024-09-17 Thread egallager at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116744 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org --- Commen

[Bug other/116744] New: RFE: can generated SARIF file be a container for "everything" needed for a bug-report against gcc?

2024-09-16 Thread hp at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116744 Bug ID: 116744 Summary: RFE: can generated SARIF file be a container for "everything" needed for a bug-report against gcc? Product: gcc Version: unknown

[Bug demangler/106622] Bug report

2022-08-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106622 --- Comment #2 from Jonathan Wakely --- Also please check whether this is a duplicate of Bug 104435, Bug 105115, Bug 106224, or Bug 106641.

[Bug demangler/106622] Bug report

2022-08-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106622 --- Comment #1 from Jonathan Wakely --- Please provide a more useful title than "Bug report". Everything in bugzilla is a bug report.

[Bug demangler/106622] New: Bug report

2022-08-15 Thread sophrosx at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106622 Bug ID: 106622 Summary: Bug report Product: gcc Version: rust/master Status: UNCONFIRMED Severity: normal Priority: P3 Component: demangler Assignee

[Bug d/103840] d: Errors message: Please submit a full bug report in testsuite

2022-01-06 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103840 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |12.0

[Bug d/103840] d: Errors message: Please submit a full bug report in testsuite

2022-01-03 Thread ibuclaw at gdcproject dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103840 Iain Buclaw changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug d/103840] d: Errors message: Please submit a full bug report in testsuite

2022-01-03 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103840 --- Comment #3 from CVS Commits --- The master branch has been updated by Iain Buclaw : https://gcc.gnu.org/g:c43b5909031c7aa32ac65df3e392a12d32c45194 commit r12-6185-gc43b5909031c7aa32ac65df3e392a12d32c45194 Author: Iain Buclaw Date: Sun J

[Bug d/103840] d: Errors message: Please submit a full bug report in testsuite

2021-12-27 Thread ibuclaw at gdcproject dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103840 --- Comment #2 from Iain Buclaw --- Fix in upstream. https://github.com/dlang/dmd/pull/13462

[Bug d/103840] d: Errors message: Please submit a full bug report in testsuite

2021-12-26 Thread ibuclaw at gdcproject dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103840 --- Comment #1 from Iain Buclaw --- In both cases, the dmd front-end has an error with %zu as a format specifier in the message.

[Bug d/103840] New: d: Errors message: Please submit a full bug report in testsuite

2021-12-26 Thread ibuclaw at gdcproject dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103840 Bug ID: 103840 Summary: d: Errors message: Please submit a full bug report in testsuite Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal

[Bug c++/79736] [5 Regression] Please submit a full bug report: unable to create precompiled headers

2018-07-15 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79736 Andrew Pinski changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug c++/79736] [5 Regression] Please submit a full bug report: unable to create precompiled headers

2018-04-20 Thread redi at gcc dot gnu.org
||4.9.4, 6.1.0 Target Milestone|--- |6.0 Summary|Please submit a full bug|[5 Regression] Please |report: unable to create|submit a full bug report: |precompiled headers |unable to

Bug Report Duplication Problem - Help !

2018-04-02 Thread amcgitirana
work since we are merely interested in learning about some aspects of your work. We are investigating the bug report duplication problem, so based on your experience using bug-trackers, we would like to invite you to participate in a short 8-10 minute survey that our research group is conduct

[Survey Invite] Bug report duplication problem - Help our study

2018-03-26 Thread amcgitirana
ince we are merely interested in learning about some aspects of your work. We are investigating the bug report duplication problem, so based on your experience using bug-trackers, we would like to invite you to participate in a short 8-10 minute survey that our research group is conductin

[Bug c++/79736] Please submit a full bug report: unable to create precompiled headers

2017-02-28 Thread x800x800 at email dot cz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79736 --- Comment #2 from x800 --- Hello, do you mean this sequence: g++ -E hdr.h -o hdr2.h g++ -fpreprocessed hdr2.h ? The same result.

[Bug c++/79736] Please submit a full bug report: unable to create precompiled headers

2017-02-28 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79736 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug c++/79736] New: Please submit a full bug report: unable to create precompiled headers

2017-02-27 Thread x800x800 at email dot cz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79736 Bug ID: 79736 Summary: Please submit a full bug report: unable to create precompiled headers Product: gcc Version: 5.4.0 Status: UNCONFIRMED Severity: normal

[Bug c++/55287] GCC crashes and asks to file bug report

2012-11-13 Thread manu at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55287 Manuel López-Ibáñez changed: What|Removed |Added CC||manu at gcc dot gnu.org --- Commen

[Bug c++/55287] GCC crashes and asks to file bug report

2012-11-13 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55287 --- Comment #5 from Jonathan Wakely 2012-11-13 09:44:26 UTC --- 6.4MB in a single function is the problem. The compiler has to process that entire function at once. And 2GB is not a great amount.

[Bug c++/55287] GCC crashes and asks to file bug report

2012-11-13 Thread gordoncichon at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55287 --- Comment #4 from Gordon Cichon 2012-11-13 08:33:01 UTC --- Why is GCC comsuming so much memory? The program has 6.4MB source code, it is a single function. All optimizations are turned off. And there is 2GB memory in the system. We

[Bug c++/55287] GCC crashes and asks to file bug report

2012-11-12 Thread paolo.carlini at oracle dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55287 --- Comment #3 from Paolo Carlini 2012-11-12 17:50:20 UTC --- Indeed.

[Bug c++/55287] GCC crashes and asks to file bug report

2012-11-12 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55287 --- Comment #2 from Andrew Pinski 2012-11-12 17:01:57 UTC --- Also this "ICE" is really the kernel killing the program as it ran out of memory or it was over one of the ulimits. Most likely ran of memory.

[Bug c++/55287] GCC crashes and asks to file bug report

2012-11-12 Thread paolo.carlini at oracle dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55287 Paolo Carlini changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|

[Bug c++/55287] New: GCC crashes and asks to file bug report

2012-11-12 Thread gordoncichon at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55287 Bug #: 55287 Summary: GCC crashes and asks to file bug report Classification: Unclassified Product: gcc Version: 4.4.5 Status: UNCONFIRMED Severity: normal

[Bug c/55084] please submit full bug report

2012-10-28 Thread mpolacek at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55084 Marek Polacek changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|

[Bug c/55084] please submit full bug report

2012-10-26 Thread mpolacek at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55084 Marek Polacek changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug c/55084] New: please submit full bug report

2012-10-26 Thread nikhildagade007 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55084 Bug #: 55084 Summary: please submit full bug report Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

[Bug fortran/42848] compiler crashes and asks for this bug report

2010-09-10 Thread fxcoudert at gcc dot gnu dot org
--- Comment #7 from fxcoudert at gcc dot gnu dot org 2010-09-10 21:08 --- Closing, please reopen with additional information if the problem persists with a more recent version of the compiler (>= 4.5.0). Thanks! -- fxcoudert at gcc dot gnu dot org changed: What|Remov

[Bug fortran/42848] compiler crashes and asks for this bug report

2010-04-30 Thread dfranke at gcc dot gnu dot org
--- Comment #6 from dfranke at gcc dot gnu dot org 2010-04-30 22:13 --- (In reply to comment #5) > The compiler shouldn't crash anyway. But with a new version this problem > should > be solved too, isn't it? It should be. 4.5.0 was released by now. Could you check again? -- dfranke

[Bug fortran/42848] compiler crashes and asks for this bug report

2010-01-25 Thread frank dot braun at rz dot uni-regensburg dot de
--- Comment #5 from frank dot braun at rz dot uni-regensburg dot de 2010-01-25 08:36 --- 've got it. Modifying the .mod file by hand makes the compiler crash. Deleting it lets it work correctly. The compiler shouldn't crash anyway. But with a new version this problem should be solved t

[Bug fortran/42848] compiler crashes and asks for this bug report

2010-01-25 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2010-01-25 08:30 --- (In reply to comment #3) > Today I am not able to reproduce the error. The compiler is working. Where > exactly does the file m.mod reside? In the user directory or in a compiler > directory? By default in the curren

[Bug fortran/42848] compiler crashes and asks for this bug report

2010-01-24 Thread frank dot braun at rz dot uni-regensburg dot de
) > Tobias, > > If we ask a bug submitter for more information, or to confirm our suspicions, > we put the bug report in WAITING. > > Note to submitter: bug reports with status WAITING will be closed if not > replied to within 3 months. > > Kind regards. > --

[Bug fortran/42848] compiler crashes and asks for this bug report

2010-01-23 Thread toon at moene dot org
--- Comment #2 from toon at moene dot org 2010-01-23 13:24 --- Tobias, If we ask a bug submitter for more information, or to confirm our suspicions, we put the bug report in WAITING. Note to submitter: bug reports with status WAITING will be closed if not replied to within 3 months

[Bug fortran/42848] compiler crashes and asks for this bug report

2010-01-22 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2010-01-22 17:44 --- Thanks for the bug report. However, I think this a duplicate of PR 40195 which was fixed 2009-05-22. Thus, the solution is to use any GCC 4.4.x or 4.5.x newer than 22 May 2009 such as 4.4.1, 4.4.2, or 4.4.3 - or a

[Bug fortran/42848] New: compiler crashes and asks for this bug report

2010-01-22 Thread frank dot braun at rz dot uni-regensburg dot de
bstdcxx-debug --ena ble-version-specific-runtime-libs --prefix=/mingw --with-gmp=/mingw/src/gmp/root --with-mpfr=/mingw/src/mpfr/root --build=mingw32 Thread-Modell: win32 gcc-Version 4.4.0 (GCC) administra...@pc6 /c/vectra/fortran -- Summary: compiler crashes and asks for this bug

[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution

2009-01-13 Thread rguenth at gcc dot gnu dot org
--- Comment #12 from rguenth at gcc dot gnu dot org 2009-01-13 22:41 --- Fixed for GCC 4.4 (with unit-at-a-time being always on). -- rguenth at gcc dot gnu dot org changed: What|Removed |Added --

[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution

2009-01-13 Thread rob1weld at aol dot com
--- Comment #11 from rob1weld at aol dot com 2009-01-13 22:10 --- ping -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886

[Bug c/38521] -masm=intel, struct output for __asm__() block causes gcc to ask for bug report.

2008-12-14 Thread ubizjak at gmail dot com
--- Comment #1 from ubizjak at gmail dot com 2008-12-14 11:18 --- There were many problems with -masm=intel, that were fixed for gcc-4.3 and later by [1] and (many) followup patches. The change that you are looking for is (gcc/config/i386/i386.c): @@ -9037,8 +9047,9 @@ print_operand (FI

[Bug c/38521] New: -masm=intel, struct output for __asm__() block causes gcc to ask for bug report.

2008-12-13 Thread vbernetr at gmail dot com
I'm currently writing a small kernel, and gcc asked me to file a bug report. I've scrapped the file from anything not directly related to the bug, which makes it quite small. I'm aware the assembly syntax is most likely wrong. Hope this is useful. Command line : ## gcc

Worth a bug report?

2008-10-17 Thread Pranith Kumar
Hello, I ran into the following using gcc 4.2.3 on ubuntu 8.04. I ran it with -Werror so it died on receiving this warning: cc1: warnings being treated as errors tux3fuse.c: In function 'tux3_lookup': tux3fuse.c:78: warning: initialized field overwritten tux3fuse.c:78: warning: (near initializati

Bug report

2008-08-03 Thread Seppo Laitinen
ase submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html> for instructions. -- file.c Description: Binary data

[Bug middle-end/36465] Compilation crashes and asks me to submit a bug report

2008-06-08 Thread pinskia at gcc dot gnu dot org
--- Comment #5 from pinskia at gcc dot gnu dot org 2008-06-08 14:12 --- fipa-pta is known to be broken, don't use it. *** This bug has been marked as a duplicate of 29212 *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added -

[Bug middle-end/36465] Compilation crashes and asks me to submit a bug report

2008-06-08 Thread pattakosn at yahoo dot com
--- Comment #4 from pattakosn at yahoo dot com 2008-06-08 14:10 --- (In reply to comment #2) > I downloaded and compiled 4.3.1 which seems to work well. I am sorry, maybe I was not clear. I meant that I downloaded and compiled 4.3.1 and 4.4-20080606 and then gfortran 4.3.1 compiles my s

[Bug middle-end/36465] Compilation crashes and asks me to submit a bug report

2008-06-08 Thread pattakosn at yahoo dot com
--- Comment #3 from pattakosn at yahoo dot com 2008-06-08 14:06 --- Created an attachment (id=15730) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15730&action=view) the file that the latest gfortran (4.4-20080606) fails to compile and the produced .s file This is the file relevan

[Bug middle-end/36465] Compilation crashes and asks me to submit a bug report

2008-06-08 Thread pattakosn at yahoo dot com
GC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 main3.f: In function ‘MAIN__.omp_fn.0’: main3.f:390: error: stmt (0xb7d02410) marked modified after optimization pass: omp_get_thread_num (); main3.f:390: internal compiler error: verify_ssa failed Please submit a full bug report, with

[Bug middle-end/36465] Compilation crashes and asks me to submit a bug report

2008-06-08 Thread pinskia at gcc dot gnu dot org
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added CC||pinskia at gcc dot gnu dot |

[Bug fortran/36465] Compilation crashes and asks me to submit a bug report

2008-06-08 Thread pattakosn at yahoo dot com
--- Comment #1 from pattakosn at yahoo dot com 2008-06-08 12:05 --- Created an attachment (id=15729) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15729&action=view) The source code and the generated .s file This is the source file that crashes and the .s file that is generated.

[Bug fortran/36465] New: Compilation crashes and asks me to submit a bug report

2008-06-08 Thread pattakosn at yahoo dot com
Bed_ini.s GNU F95 (GCC) version 4.3.0 (i686-pc-linux-gnu) compiled by GNU C version 4.3.0, GMP version 4.2.2, MPFR version 2.3.1. GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 Bed_ini.f: In function ‘pr9_bed’: Bed_ini.f:206: internal compiler error: in get_smt_for,

[Bug fortran/34837] gfortran crashes and asks for bug report

2008-01-17 Thread pinskia at gcc dot gnu dot org
--- Comment #4 from pinskia at gcc dot gnu dot org 2008-01-18 02:24 --- WRITE (label,'(I4,A)') 2**2.0 This is what is crashing. I fixed this with PR 29982 over a year ago :). *** This bug has been marked as a duplicate of 29982 *** -- pinskia at gcc dot gnu dot org changed:

[Bug fortran/34837] gfortran crashes and asks for bug report

2008-01-17 Thread kargl at gcc dot gnu dot org
--- Comment #3 from kargl at gcc dot gnu dot org 2008-01-18 01:32 --- (In reply to comment #2) > I have installed > gcc version 4.3.0 20071231 (experimental) [trunk revision 131236] (GCC) > and the error goes away. I can turn it on and off by switching between > the two, though it is no

[Bug fortran/34837] gfortran crashes and asks for bug report

2008-01-17 Thread skinner at milkyway dot gsfc dot nasa dot gov
--- Comment #2 from skinner at milkyway dot gsfc dot nasa dot gov 2008-01-18 00:49 --- Subject: Re: gfortran crashes and asks for bug report burnus at gcc dot gnu dot org wrote: > --- Comment #1 from burnus at gcc dot gnu dot org 2008-01-17 22:45 > --- > Thanks fo

[Bug fortran/34837] gfortran crashes and asks for bug report

2008-01-17 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2008-01-17 22:45 --- Thanks for the bug report; however, I fail to reproduce the bug with either of 4.1.3, 4.2.2 and 4.3.0 on x86-64-linux. Your version "4.2.0 (experimental)" is relatively old. (Even 4.1.3 might contain

[Bug fortran/34837] New: gfortran crashes and asks for bug report

2008-01-17 Thread skinner at milkyway dot gsfc dot nasa dot gov
> gfortran -c makeplot.f90 makeplot.f90: In function 'MAIN__': makeplot.f90:103: internal compiler error: in expand_expr_addr_expr_1, at expr.c:6517 Please submit a full bug report, with preprocessed source if appropriate. __ gfortran -v Using built-in specs. Targe

[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution

2007-08-20 Thread rguenth at gcc dot gnu dot org
--- Comment #10 from rguenth at gcc dot gnu dot org 2007-08-20 07:58 --- Honza, can you look into this pls? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886

[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution

2007-08-06 Thread zhouyi04 at ios dot cn
--- Comment #9 from zhouyi04 at ios dot cn 2007-08-06 08:40 --- (In reply to comment #8) I try to compile my giving C program using gcc-4.2.1, the problem still exists. As my solution 1 suggests: a caller function is inlinable only if all of its callee functions are inlinable. while thi

[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution

2007-08-05 Thread rob1weld at aol dot com
--- Comment #8 from rob1weld at aol dot com 2007-08-06 06:44 --- GCC 4.2.2 20070804 is able to compile newer kernels as is 4.2.1 20070628. I guess 4.3 and 4.1 are the only series lacking this ability. I am not allowed to change the "Summary:" to add "[4.3 Regression]" to the begining s

[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution

2007-08-02 Thread rob1weld at aol dot com
--- Comment #7 from rob1weld at aol dot com 2007-08-02 17:24 --- Created an attachment (id=14010) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14010&action=view) Example of kernel file that causes "inlining failed" error -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886

[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution

2007-08-02 Thread rob1weld at aol dot com
--- Comment #6 from rob1weld at aol dot com 2007-08-02 17:18 --- I can confirm this too. Here is the bug report I was to post - but I searched to see if this was already reported ;) - Here are my notes: tree-inline.c - sorry, unimplemented: inlining failed ... function body not

[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution

2007-05-10 Thread rguenth at gcc dot gnu dot org
--- Comment #5 from rguenth at gcc dot gnu dot org 2007-05-10 11:04 --- Confirmed. Either we should not accept always_inline on a function not declared inline (or warn in that case), or a function marked always_inline should be considered for inlining always. Second, the t.i:3: sorry,

[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution

2007-05-09 Thread zhouyi04 at ios dot cn
--- Comment #4 from zhouyi04 at ios dot cn 2007-05-10 05:33 --- Dear Pinsky In addition, The problem will still exists even add a inline to line 1 of the program, unless you add a static to line 1. Sincerely yours Zhouyi Zhou -- zhouyi04 at ios dot cn changed: What|

[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution

2007-05-09 Thread zhouzhouyi at ercist dot iscas dot ac dot cn
--- Comment #3 from zhouzhouyi at ercist dot iscas dot ac dot cn 2007-05-10 04:43 --- Subject: Re: (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution heh, pinkia, take a look at my solution1 On 10 May 2007 03:41:06 -

[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution

2007-05-09 Thread zhouzhouyi at ercist dot iscas dot ac dot cn
--- Comment #2 from zhouzhouyi at ercist dot iscas dot ac dot cn 2007-05-10 04:41 --- Subject: Re: (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution Dear pinskia, If you lookup my solution current handling of conditions for

[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution

2007-05-09 Thread pinskia at gcc dot gnu dot org
dot org changed: What|Removed |Added Status|UNCONFIRMED |WAITING Summary|(different from bug report |(different from bug report |c/310

[Bug c/31886] New: (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution

2007-05-09 Thread zhouyi04 at ios dot cn
) +inlinable = true; DECL_UNINLINABLE (fn) = !inlinable; return inlinable; /*** *******/ Sincerely yours Zhouyi Zhou -- Summary: (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution Product: gcc

gcc-bug-report- Tuesday May 08 - Portugal

2007-05-08 Thread Miguel Luis
According to http://gcc.gnu.org/bugs.html here is what is requested for a bug report. Regards, Miguel Luis. ## the exact version of GCC; $ gcc --version gcc (GCC) 4.1.2 (Ubuntu 4.1.2-0ubuntu4) Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying

bug report

2007-02-21 Thread Fabio TROVATO
ione.f:806: internal compiler error: in instantiate_virtual_regs_lossage, at function.c:3746 Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html> for instructions. This is it. I don't know if you need a copy of the program NEWdistr_A

Re: GCC bug report - Xubuntu kernel compile fails w/gcc bug report request

2007-01-25 Thread Jim Wilson
Jonathan Brickman wrote: as indicated by anyone who knows what I should be trying next! I tried to send this via the GCC web bug report system, but I could not find any way to attach this file, which the docs said is essential. First file the bug report, you will then immediately be taken to

BUG report : Internal compiler error

2006-11-03 Thread R.J.Sivakumar
hi this is the error iam getting when i try to cross compile ltib BSP of linux 2.6.10 for arm11 platfrom from SUSE10 host arm-none-linux-gnueabi-ranlib ./libgcov.a arm-none-linux-gnueabi-gcc -O2 -DIN_GCC-W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-styl

bug report

2006-10-04 Thread ZiZi Zhao
1. configure options: alfalfa:/home/zz/share/gcc.4.1/gcc-4.1.1:{1193} ./configure --prefix= $HOME/local 2. make stage1 gcc-4.1.1 alfalfa:/home/zz/share/gcc.4.1/gcc-4.1.1:{1193} make boostrap ... ... (stop at) /home/zz/share/gcc.4.1/gcc-4.1.1/host-i386-redhat-linux/gcc/xgcc - shared-libgcc -B/ho

bug report

2006-09-12 Thread poczta-sn
a bug in mingw //this shows that the older version of mingw32 can be better than the newer one #include #include #include main() { //the string should be written two times if the file exists ifstream xyz; char chr; xyz.open("a.bat"); while(xyz.get(chr)) cout<

Re: bug report

2006-06-08 Thread Hayashi Eisuke
DEAR Sir : GNU I am writing to you regarding bug report It resulted based on the last point when having experimented ..the following... #include #include void subroutine(int n) { int buf[n]; fprintf(stderr, "%d (%d)\n", (int)sizeof(buf), (unsigned long)buf); } int main

Re: bug report

2006-06-08 Thread Jim Wilson
Hayashi Eisuke wrote: > 100: 400 (-1077752048) > 2092728: Segmentatioin error (core dumped) The process is dying because you are exceeding unix process stack space limits. You probably have an 8MB per process limit, and the number you are using is a tad less than 2MB. If you are using ba

bug report

2006-06-07 Thread Hayashi Eisuke
DEAR Sir : GNU I am writing to you regarding bug report under this code #include #include void subroutine(int n) { int buf[n]; fprintf(stderr, "%d (%d)\n", (int)sizeof(buf), (unsigned long)buf); } int main( int argc, char **argv) { int i, value[] = {0, 1, -

Re: bug report

2006-06-07 Thread Andrew Pinski
Hi Hayashi-san, I am writing to you regarding bug report about under this code aaa(int bbb) {   char *ccc[bbb]     } gcc response no error.  but memory error occured. GCC accepts this as an extension to the ISO C 90 and ISO C++ languages by default. The extension is called Variable

bug report

2006-06-07 Thread Hayashi Eisuke
DEAR  Sir : GNU I am writing to you regarding bug report about under this code aaa(int bbb) {   char *ccc[bbb]     } gcc response no error.  but memory error occured. Sincerely yours, EISUKE HAYASHI

Bug report - unrecognizable insn

2006-03-22 Thread James Steward
t:SI (reg/v:SI 5 r5 [orig:557 i ] [557]) (const_int 4 [0x4])) (reg/v/f:SI 8 r8 [orig:85 z ] [85])) [3 S4 A32])) -1 (nil) (nil)) s_depth.c:1362: internal compiler error: in extract_insn, at recog.c:2083 Please submit a full bug report, with preprocessed source

gcc 4.0.2 bug report

2006-01-23 Thread Stephan . Beal . extern
Hi, gcc team! i unfortunately cannot use the bug db for this report because i am not allowed to use this email address for websites, mailing lists, etc. Bug summary: The two-arg form of std::random_shuffle() shuffles predictably unless srand() is called beforehand. GCC version: gcc (GCC) 4.0.2 C

GCC bug report: incorrect assertion in PCH

2005-12-06 Thread Edward Chernenko
I'm describing a error which occures when running GCC 4.0.2 compiled with internal coverage checks (when gcc_assert() produces code). There is a place in 'ggc-common.c' at line 870: > gcc_assert (!*slot); This assertion ALWAYS fail when using the PCH. I think it must be removed. Edward Chernen

Re: Compiler bug report

2005-10-18 Thread Jim Wilson
here. You can try contacting the people you got the compiler release from, or you can try an FSF gcc release. please! anyone suggest me the bug fix for this problem... now i am pasting the error report which i got while building the kernel image. This bug report is lacking info we normally

Compiler bug report

2005-10-18 Thread goutamkumar
ning: ignoring pragma: locks.c: In function `flock_make_lock': locks.c:239: Internal compiler error in `output_move_double', at config/arm/arm.c:5125 Please submit a full bug report. See http://www.gnu.org/software/gcc/faq.html#bugreport> for instructions. arm-elf-gcc: Internal compi

Compiler bug report

2005-10-18 Thread Mitul Shah
: In function `flock_make_lock': locks.c:239: Internal compiler error in `output_move_double', at config/arm/arm.c:5125 Please submit a full bug report. See http://www.gnu.org/software/gcc/faq.html#bugreport> for instructions. arm-elf-gcc: Internal compiler error: program cpp got fatal sign

Re: gfortran says to submit bug report

2005-09-28 Thread Andrew Pinski
On Sep 28, 2005, at 4:53 PM, Joe Koski wrote: While attempting to compile the NIST FDS4 code (f90 based) I get the following error and a request to submit a bug report: jakoski$ gfortran -c -O3 -ffixed-form -fno-underscoring mods.f mods.f: In function 'lpcoef': mods.f:5

[Bug c/21446] internal compiler error -- is recommending to file a bug report

2005-05-07 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-07 19:33 --- *** This bug has been marked as a duplicate of 9382 *** -- What|Removed |Added

[Bug c/21446] New: internal compiler error -- is recommending to file a bug report

2005-05-07 Thread philip dot thambidurai at comverse dot com
Trying to build gcc-3.4.3 for IBM AIX 5.3L on an IBM p570 machine. Fails, and a message asks me to file a bug report. I have generated the .i file using ./xgcc -v -save-temps ... ... but I don't see a way to attach the .i file (and .s file if you need) in this Bugzilla form. I can email

Re: bug report for gfortran

2005-04-28 Thread Andrew Pinski
On Apr 28, 2005, at 2:41 PM, Dutta, Kalyan wrote: I am submitting a bug report for GNU's Fortran95 compiler, gfortran. I realize the compiler is experimental. Any help you might be able to provide will be appreciated. I am Emailing this report because I couldn't successfully attach the

GCC bug report

2004-11-19 Thread Gerhard Jacobs
(const_int -7 [0xfff9])) [0 J1_CRC_Byte S1 A8])) 37 {*m68k.md:1060} (nil) (nil)) 2m_tpl.c:84: internal compiler error: in reload_cse_simplify_operands, at reload1.c:8353 Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html> for instructions. 2m_tpl.c Description: Binary data 2m_tpl.i Description: Binary data

[Bug c++/18203] Compiler suggests submitting a bug report after exiting while printing error message

2004-10-28 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-10-28 16:56 --- If the problem only occurs in 3.2 and not in 3.2.2, the problem is already fixed. -- What|Removed |Added -

[Bug c++/18203] Compiler suggests submitting a bug report after exiting while printing error message

2004-10-28 Thread ron at vaniwaarden dot org
--- Additional Comments From ron at vaniwaarden dot org 2004-10-28 16:54 --- (In reply to comment #0) Problem does not occur with g++ 3.2.2 or 3.4.1 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18203

[Bug c++/18203] New: Compiler suggests submitting a bug report after exiting while printing error message

2004-10-28 Thread ron at vaniwaarden dot org
The following should compile with an error message but the compiler dies in the middle of printing an error message #include template std::basic_ostream(charT)& operator<<(std::basic_ostream& os); -- Summary: Compiler suggests submitting a bug report

[Bug c++/18201] Compiler suggests submitting a bug report after exiting while printing error message

2004-10-28 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-10-28 16:30 --- Fixed since 3.2.2: pr18201.cc:4: error: invalid use of template-name 'std::basic_ostream' in a declarator pr18201.cc:4: error: syntax error before `&' token pr18201.cc:4: error: `charT' was not declared

[Bug c++/18201] New: Compiler suggests submitting a bug report after exiting while printing error message

2004-10-28 Thread ron at vaniwaarden dot org
The following should compile with an error message but the compiler dies in the middle of printing an error message #include template std::basic_ostream(charT)& operator<<(std::basic_ostream& os); -- Summary: Compiler suggests submitting a bug report

Re: gfortran internal compiler error - "Please submit a full bug report" being attempted

2004-10-20 Thread Andrew Pinski
On Oct 20, 2004, at 9:21 AM, Gordon Sande wrote: Reporting the bug requires setting up my 1,070,045th user account somewhere so I will use the email version as the gccbug script exists somewhere else. Mac Os X 10.3.5 Dual 1.8 G5 Mac standard configuration, i.e middle model before first speed bu

gfortran internal compiler error - "Please submit a full bug report" being attempted

2004-10-20 Thread Gordon Sande
imental) g5Mac:~/Cmd/gfortran gordon$ gfortran gfortran_bug.f90 gfortran_bug.f90: In function `initch': gfortran_bug.f90:0: internal compiler error: in check_pointer_types_r, at gimplify.c:4261 Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.

Re: gfortran says to submit bug report

2004-10-11 Thread Joe Koski
Andrew, After reading 17917, I agree. Thanks for your reply. Joe Koski on 10/11/04 11:03 AM, Andrew Pinski at [EMAIL PROTECTED] wrote: > > On Oct 11, 2004, at 12:38 PM, Joe Koski wrote: > >> backend decl for module variable > > > This is most likely the same as PR 17917. > > Thanks, > And

Re: gfortran says to submit bug report

2004-10-11 Thread Andrew Pinski
On Oct 11, 2004, at 12:38 PM, Joe Koski wrote: backend decl for module variable This is most likely the same as PR 17917. Thanks, Andrew Pinski

gfortran says to submit bug report

2004-10-11 Thread Joe Koski
submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html> for instructions. make: *** [mods.o] Error 1 No "preprocessed source" appeared when I added -save-temps to the compile line. The compiler info is pcp05454784pcs:~/Codes/For