https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61262
--- Comment #1 from lailavrazda1979 at gmail dot com ---
A bug that causes GCC to segfault AND is a regression is only normal in
severity? I thought a crash is one of those things that should never, EVER
happen?
: unassigned at gcc dot gnu.org
Reporter: lailavrazda1979 at gmail dot com
Since I code, I know that this is gonna be a pretty bad bug report. But I know
next to nothing about the code I'm compiling, however, what I do know is, GCC
4.8.x works, while GCC 4.9.0 segfaults. Since I don't kno
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57926
lailavrazda1979 at gmail dot com changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57926
--- Comment #16 from lailavrazda1979 at gmail dot com ---
Okay, no worries.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57926
--- Comment #14 from lailavrazda1979 at gmail dot com ---
Why wait? I'm not hugely opposed, but bugfixes are bugfixes, and one more fixed
bug makes a better 4.9 release, right?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57926
--- Comment #12 from lailavrazda1979 at gmail dot com ---
Bug still a problem with latest trunk.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57926
--- Comment #11 from lailavrazda1979 at gmail dot com ---
I don't mean to be a bother, but this hasn't been updated in a while. Has it
been fixed?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57926
--- Comment #10 from lailavrazda1979 at gmail dot com ---
Is this going to be fixed?
nt: c
Assignee: unassigned at gcc dot gnu.org
Reporter: lailavrazda1979 at gmail dot com
You guys consider checking for 0.10 and up instead of adding an explicit check
for every new release?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57926
--- Comment #1 from lailavrazda1979 at gmail dot com ---
Created attachment 30523
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30523&action=edit
Code triggering the bug
++
Assignee: unassigned at gcc dot gnu.org
Reporter: lailavrazda1979 at gmail dot com
Note that this possible bug does not trigger with GCC, only G++.
Try compiling the code in the attachment with g++. It'll give strange errors,
including complaining that an argument must be
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57630
--- Comment #3 from lailavrazda1979 at gmail dot com ---
Looks good to me.
Assignee: unassigned at gcc dot gnu.org
Reporter: lailavrazda1979 at gmail dot com
The following message:
"error: 'for' loop initial declarations are only allowed in C99 mode
minigen.c:88:2: note: use option -std=c99 or -std=gnu99 to compile your code"
should in
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56057
lailavrazda1979 at gmail dot com changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55819
lailavrazda1979 at gmail dot com changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56057
Bug #: 56057
Summary: libbacktrace STILL doesn't honor --disable-werror
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56042
--- Comment #2 from lailavrazda1979 at gmail dot com 2013-01-20 02:13:29 UTC ---
Strange, it seems to work with the last release of mingw-w64. I configured the
headers with:
./configure --build=$CROSS_HOST --host=$CROSS_TGT --prefix
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56042
Bug #: 56042
Summary: Many errors building GCC trunk with mingw-w64 rev.
5542
Classification: Unclassified
Product: gcc
Version: unknown
Status: UNCONFIRMED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925
lailavrazda1979 at gmail dot com changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925
--- Comment #6 from lailavrazda1979 at gmail dot com 2013-01-14 23:18:30 UTC ---
So, you need GCC 4.8 to build GCC 4.8? That's just... why? Doesn't that mean
it's basically impossible to build GCC 4.8 without a binary of it first?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925
--- Comment #4 from lailavrazda1979 at gmail dot com 2013-01-14 21:26:36 UTC ---
I tried building several compilers (4.7.2), none of which understand the
'-mfxsr' option. One was configured with:
../gcc-4.7.2/configure --bu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925
--- Comment #2 from lailavrazda1979 at gmail dot com 2013-01-13 23:31:01 UTC ---
How did I configure which GCC? The cross compiler or the native one?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925
Bug #: 55925
Summary: Unrecognized command line option '-mfxsr' when
building x86_64-w64-mingw32 native compiler
Classification: Unclassified
Product: gcc
Version: 4.8.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55819
--- Comment #2 from lailavrazda1979 at gmail dot com 2012-12-31 19:42:19 UTC ---
I know it works with 4.7.2, and I think 4.7.3 as well.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55819
Bug #: 55819
Summary: Conflicting declaration of getcwd breaks mingw-w64
compile
Classification: Unclassified
Product: gcc
Version: unknown
Status: UNCONFIR
25 matches
Mail list logo
