[Bug libstdc++/56785] std::tuple of two elements does not apply empty base class optimization when one of its elements is a std::tuple with two elements

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56785 --- Comment #1 from Marc Glisse glisse at gcc dot gnu.org 2013-03-30 09:06:44 UTC --- I assume (needs to be checked) this is related to the issue, reported elsewhere, that makes the size of std::tuplestd::tuplestd::tuplestd::tuple grow

[Bug target/50829] avx extra copy for _mm256_insertf128_pd

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50829 --- Comment #13 from Marc Glisse glisse at gcc dot gnu.org 2013-03-30 10:13:46 UTC --- (In reply to comment #10) Created attachment 28846 [details] Use subreg The patch was submitted at

[Bug libfortran/56786] New: [4.6/4.7/4.8/4.9 Regression] Namelist read fails with designators containing embedded spaces

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56786 Bug #: 56786 Summary: [4.6/4.7/4.8/4.9 Regression] Namelist read fails with designators containing embedded spaces Classification: Unclassified Product: gcc Version:

[Bug fortran/52512] Cannot match namelist object name

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52512 --- Comment #7 from Tobias Burnus burnus at gcc dot gnu.org 2013-03-30 10:18:48 UTC --- (In reply to comment #6) This bug fixed by Tilo's patch. Closing. Jerry, please read the PRs carefully before you close them. The issue in

[Bug fortran/56743] Namelist bug with comment and no blank

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56743 --- Comment #4 from Tobias Burnus burnus at gcc dot gnu.org 2013-03-30 10:47:30 UTC --- Created attachment 29752 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=29752 Test case - please read comment in the file or comment 4 The test

[Bug other/56721] libffi.info installed in share/info collides with that from libffi itself

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56721 Matthias Klose doko at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug target/48326] Target attribute leaks from function pointers

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48326 --- Comment #3 from Mikael Pettersson mikpe at it dot uu.se 2013-03-30 11:59:19 UTC --- I can reproduce the initial bug with gcc 4.4.7, 4.5.3, 4.6.3, and 4.7.0, but not with 4.5.4, 4.6-20130322, 4.7.1, or 4.7.2.

[Bug debug/56783] g++ does not supply signatures for gdb on g++ 4.7 versions

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56783 Jonathan Wakely redi at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug target/48326] Target attribute leaks from function pointers

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48326 --- Comment #4 from Mikael Pettersson mikpe at it dot uu.se 2013-03-30 12:31:38 UTC --- The initial bug was fixed by r187169 on 4.7 branch, I'd say it's clearly a dup of PR53228.

[Bug c/52952] Wformat location info is bad (wrong column number)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52952 --- Comment #15 from Manuel López-Ibáñez manu at gcc dot gnu.org 2013-03-30 12:32:08 UTC --- (In reply to comment #13) I guess the C/C++ FEs could for non-trivial string literals put into a hash table mapping from locus_t (of ADDR_EXPR around

[Bug c/52952] Wformat location info is bad (wrong column number)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52952 --- Comment #16 from Manuel López-Ibáñez manu at gcc dot gnu.org 2013-03-30 12:32:57 UTC --- Created attachment 29753 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=29753 loc_token_hash

[Bug c/52952] Wformat location info is bad (wrong column number)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52952 Manuel López-Ibáñez manu at gcc dot gnu.org changed: What|Removed |Added CC||joseph at

[Bug c/52952] Wformat location info is bad (wrong column number)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52952 --- Comment #18 from stevenb.gcc at gmail dot com stevenb.gcc at gmail dot com 2013-03-30 12:54:12 UTC --- * It would be extremely nice to update the testsuite to check the locations are correct. This is unfortunately a lot of boring

[Bug c/52952] Wformat location info is bad (wrong column number)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52952 --- Comment #19 from Manuel López-Ibáñez manu at gcc dot gnu.org 2013-03-30 13:26:19 UTC --- Unfortunately, there are some stuff like this: addr_expr 0x7708f680 type pointer_type 0x77094690 type array_type 0x77094540

[Bug libfortran/49791] [4.6/4.7/4.8/4.9 Regression] Formatted namelist reads fails with: Cannot match namelist object

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49791 Tobias Burnus burnus at gcc dot gnu.org changed: What|Removed |Added CC||burnus

[Bug fortran/56660] Fails to read NAMELIST with certain form array syntax

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56660 Tobias Burnus burnus at gcc dot gnu.org changed: What|Removed |Added CC||burnus

[Bug debug/56783] g++ does not supply signatures for gdb on g++ 4.7 versions

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56783 --- Comment #9 from Dick Guertin dick.guertin at gmail dot com 2013-03-30 14:52:33 UTC --- (In reply to comment #8) (In reply to comment #6) First, my apology for not giving the gdp version. I assume you meant this: GNU gdb

[Bug c/56787] New: 4.8.0 Vectorization Regression Compared to 4.7.2

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56787 Bug #: 56787 Summary: 4.8.0 Vectorization Regression Compared to 4.7.2 Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/56735] [4.6/4.7/4.8/4.9 Regression] Namelist Read Error with question marks

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56735 --- Comment #8 from Tobias Burnus burnus at gcc dot gnu.org 2013-03-30 15:00:11 UTC --- The issue has been fixed on the 4.9 development branch - and it is scheduled for backporting to the 4.6, 4.7 and 4.8 release branches. See

[Bug c/52952] Wformat location info is bad (wrong column number)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52952 --- Comment #20 from Manuel López-Ibáñez manu at gcc dot gnu.org 2013-03-30 15:02:11 UTC --- (In reply to comment #18) * It would be extremely nice to update the testsuite to check the locations are correct. This is unfortunately a lot of

[Bug c/52952] Wformat location info is bad (wrong column number)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52952 --- Comment #21 from Manuel López-Ibáñez manu at gcc dot gnu.org 2013-03-30 15:03:14 UTC --- Created attachment 29755 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=29755 add locations and offsets to format warnings My current patch,

[Bug fortran/56735] [4.6/4.7/4.8/4.9 Regression] Namelist Read Error with question marks

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56735 --- Comment #9 from Adam Williams madawilliams at gmail dot com 2013-03-30 18:42:44 UTC --- This is great. I look forward to testing when I get a chance to build from the latest dev branch. I understand what you mean with the ?, however

[Bug target/56788] New: _mm_frcz_sd and _mm_frcz_ss ignore their second argument

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56788 Bug #: 56788 Summary: _mm_frcz_sd and _mm_frcz_ss ignore their second argument Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED

[Bug target/56788] _mm_frcz_sd and _mm_frcz_ss ignore their second argument

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56788 --- Comment #1 from Marc Glisse glisse at gcc dot gnu.org 2013-03-30 20:42:51 UTC --- _mm_frcz_ss is inconsistent between compilers. Microsoft gives it 2 arguments and movss-like semantics, whereas clang gives it a single argument. AMD

[Bug c++/51440] Improve message and add an option for warning for an unnamed struct member: TYPE has a field FIELD whose type uses the anonymous namespace

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51440 --- Comment #5 from Martin Richtarsky gcc at martinien dot de 2013-03-30 22:06:48 UTC --- Hi Manuel, thanks for the pointers how to add the optional warning. I will try to submit a patch, however first I would like to understand what is

[Bug fortran/56789] New: Wrong code with contiguous dummy argument

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789 Bug #: 56789 Summary: Wrong code with contiguous dummy argument Classification: Unclassified Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/56789] Wrong code with contiguous dummy argument

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789 Thomas Koenig tkoenig at gcc dot gnu.org changed: What|Removed |Added CC||burnus

[Bug tree-optimization/56790] New: VEC_COND_EXPR not constant folded

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56790 Bug #: 56790 Summary: VEC_COND_EXPR not constant folded Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Keywords: missed-optimization

[Bug bootstrap/56714] [4.9 regression] Bootstrap failure libitm/local_atomic:1580:3: error: always_inline function might not be inlinable

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56714 Jan Hubicka hubicka at gcc dot gnu.org changed: What|Removed |Added CC||hubicka

[Bug bootstrap/56714] [4.9 regression] Bootstrap failure libitm/local_atomic:1580:3: error: always_inline function might not be inlinable

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56714 --- Comment #2 from Gerald Pfeifer gerald at pfeifer dot com 2013-03-30 23:35:26 UTC --- Created attachment 29756 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=29756 Pre-processed source aatree.ii All those always_inline attributes

[Bug middle-end/56791] New: Segmentation fault in stage2 gengenrtl -- Incorrect instruction sequence generated by reload

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56791 Bug #: 56791 Summary: Segmentation fault in stage2 gengenrtl -- Incorrect instruction sequence generated by reload Classification: Unclassified Product: gcc Version: