http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58909
Bug ID: 58909
Summary: C++11's condition variables fail with static linkin
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compone
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58508
--- Comment #5 from Cong Hou ---
I guess I should add
/* { dg-require-effective-target vect_int } */
to the test case. It is right?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58908
Bug ID: 58908
Summary: intern compile error
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unass
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58867
--- Comment #2 from Andrew Pinski ---
Created attachment 31101
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31101&action=edit
Patch which I am testing
This is the patch which I am testing right now.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58744
--- Comment #3 from Marco Vanotti ---
(In reply to Richard Biener from comment #2)
> Confirmed. On i?86 we properly do a 16byte and a 8byte access (but we copy
> to stack anyway).
>
Yes, if the value is passed on the stack, it gets copied right.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58687
--- Comment #8 from joseph at codesourcery dot com ---
Thanks for working on this bug. http://gcc.gnu.org/contribute.html
describes how to submit changes (including testcases etc.).
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58887
--- Comment #10 from joseph at codesourcery dot com ---
On Mon, 28 Oct 2013, mtewoodbury at gmail dot com wrote:
> (Stop the 'we'! Name or enumerate the group involved please.)
Well-established consensus among the GCC maintainers about what sor
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58687
--- Comment #7 from Max TenEyck Woodbury ---
I have a patch written and I am testing it now.
What steps (other than posting it here when the tests are done) need to be done
to get it applied?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58887
--- Comment #9 from Max TenEyck Woodbury ---
(In reply to jos...@codesourcery.com from comment #7)
> On Sun, 27 Oct 2013, mtewoodbury at gmail dot com wrote:
>
>> That has not always stopped you all in the past, but that is really neither
>
> We
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58906
Tobias Burnus changed:
What|Removed |Added
Keywords||ice-on-valid-code
Status|UNCO
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58907
--- Comment #1 from Paul Pluzhnikov ---
For some reason "make" didn't update the version stamp.
make clean && make
Same problem with current trunk:
g++ (GCC) 4.9.0 20131028 (experimental)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58907
Bug ID: 58907
Summary: [c++11] ICE in gimplify_var_or_parm_decl, at
gimplify.c:
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58906
Bug ID: 58906
Summary: SELECT TYPE with CLASS IS generates ICE
Product: gcc
Version: 4.8.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58079
Uroš Bizjak changed:
What|Removed |Added
Target|mips64r5900el-linux-gnu |mips64r5900el-linux-gnu,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58079
Uroš Bizjak changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58892
Uroš Bizjak changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58079
Uroš Bizjak changed:
What|Removed |Added
CC||mcree at orcon dot net.nz
--- Comment #9 fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5
Paolo Carlini changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58892
Uroš Bizjak changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
-flto' LDFLAGS='-flto -fuse-linker-plugin'
Thread model: posix
gcc version 4.9.0 20131028 (experimental) (GCC)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58904
Bug ID: 58904
Summary: ICE: accessing a component field of an unavailable
type results in a seg fault
Product: gcc
Version: 4.8.2
Status: UNCONFIRMED
Severity: n
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54485
--- Comment #4 from Paolo Carlini ---
Patch here: http://gcc.gnu.org/ml/gcc-patches/2013-08/msg01435.html
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58887
--- Comment #8 from joseph at codesourcery dot com ---
(And for recursion, even specification at the level of standard text might
leave something to be desired; I'd think specification at the level of
X3J11/86-196, the algorithm GCC tries to fol
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58887
--- Comment #7 from joseph at codesourcery dot com ---
On Sun, 27 Oct 2013, mtewoodbury at gmail dot com wrote:
> That has not always stopped you all in the past, but that is really neither
We have plenty of experience dealing with the consequen
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58123
asmwarrior changed:
What|Removed |Added
CC||asmwarrior at gmail dot com
--- Comment #3 f
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49951
--- Comment #20 from asmwarrior ---
Hi, all. After the conversation on GDB IRC with GDB developer Jan Kratochvil, a
simple test code supplied by Jan in his bug report on
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58123#c0 can easily demonstrate
t
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58887
--- Comment #6 from Max TenEyck Woodbury ---
I have checked the code in libcpp. The __VA_ARG_COUNT__/__VA_ARGC__
implementation looks quite feasible. The heaviest impact looks to be new and
revised error messages and their translation.
I starte
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58903
Bug ID: 58903
Summary: ICE: SIGSEGV in hash_table::find_slot_with_hash() with
-O -fdevirtualize-speculatively
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Sev
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58902
Bug ID: 58902
Summary: small matrix multiplication non vectorized
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-op
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58901
Bug ID: 58901
Summary: vax bootstrap fails on subreg reload
Product: gcc
Version: 4.8.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58899
Paolo Carlini changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58442
--- Comment #10 from Martin Husemann ---
Matt Thomas suggested to go with the easy solution for now: protect the calls
with MEM_P, i.e.: change the ! mode_dependent_address_p() in the bitfield
patterns to
(MEM_P(..) && ! mode_dependent_address_p
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49951
--- Comment #19 from asmwarrior ---
Hi, I see this bug happens at least in GCC 4.8.2 again. I'm using MinGW-Build
GCC 4.8.2 under Windows, and debug Codeblocks. I have a source code which have
something like:
void CompilerGCC::SetupEnvironment()
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58831
--- Comment #16 from Zhendong Su ---
(In reply to Eric Botcazou from comment #15)
> Fixed everywhere (and twice to be really sure :-)
Verified (also against the original tests). Thanks.
34 matches
Mail list logo