https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61644
Bug ID: 61644
Summary: [4.10 Regression] ICE with LTO in expand_expr_real_1
Product: gcc
Version: 4.10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61643
Bug ID: 61643
Summary: [C++11] std::uncaught_exception returns wrong values
after std::rethrow_if_nested
Product: gcc
Version: 4.10.0
Status: UNCONFIRMED
Severi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61640
--- Comment #5 from Jerry DeLisle ---
Author: jvdelisle
Date: Sun Jun 29 02:49:45 2014
New Revision: 212118
URL: https://gcc.gnu.org/viewcvs?rev=212118&root=gcc&view=rev
Log:
2014-06-28 Jerry DeLisle
PR libgfortran/61640
* io/list_re
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850
--- Comment #25 from Tom Tromey ---
(In reply to Manuel López-Ibáñez from comment #24)
> There is a patch for GCC that was basically approved in January:
> https://gcc.gnu.org/ml/gcc-patches/2014-01/msg01284.html
>
> I am not sure why it hasn't
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61640
--- Comment #4 from Jerry DeLisle ---
Full patch submitted to gfortran list. The problem found in this PR was masking
a problem in eat_spaces for KIND=4. Was missing some parenthesis for the
indexing into the internal unit.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61642
Bug ID: 61642
Summary: g++ confuses template member template function with
template class
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61641
--- Comment #2 from John David Anglin ---
Created attachment 33029
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33029&action=edit
opt_vectorize.ii.241r.dbr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61641
--- Comment #1 from John David Anglin ---
Created attachment 33028
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33028&action=edit
opt_vectorize.ii.240r.barriers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61641
Bug ID: 61641
Summary: [4.9 Regression] undefined label in jump_table_data
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Componen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59766
--- Comment #4 from Felix Fontein ---
I can confirm this bug for GCC 4.9.0 20140604 (prerelease).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61640
--- Comment #3 from Dominique d'Humieres ---
I also confirm comment 2.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61640
--- Comment #2 from Jerry DeLisle ---
One subtlety. If I change the read to:
read(source,*) (x(i), i=1,9) ! 9 instead of 6
I get an EOF with kind=4 but the read is OK with kind=1.
I am investigating this. Probably yet another unrelated prob
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61635
--- Comment #6 from Jan Hubicka ---
> Yes it uses -fno-toplevel-reordering to avoid the problems with the
> initializer
> reordering.
>
> I tried some workarounds for this, but nothing worked so far. Likely would
> need
> a noreorder attribute
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61632
--- Comment #3 from Dominique d'Humieres ---
With the following reduced test
program p
CHARACTER(3), save :: ZTYP(3)
DATA ZTYP /'XXX','YYY','ZZZ'/
write(*,600,IOSTAT=iosa) 0.0,ZTYP
if (iosta /= 0) print *, 'error'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61640
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61637
--- Comment #10 from David Edelsohn ---
Exceptions had been working. There is no wholesale failure of exceptions in the
G++ testsuite. I also don't know why you are defining macros for Linux and
AMD, or why you think that randomly adding linker
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51400
Paolo Carlini changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #2 from Paolo Carli
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61640
Bug ID: 61640
Summary: KIND=4 Character Array Internal Unit Read Fail
Product: gcc
Version: 4.10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61637
--- Comment #9 from Krishnamoorthy C ---
(In reply to Paolo Carlini from comment #8)
> Something else besides AIX 7.1. Fore sure all the Linux targets are fine,
> for example. This isn't a generic C++ front-end issue.
The program works fine on a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=17277
Krishnamoorthy C changed:
What|Removed |Added
CC||chandrakm at hotmail dot com
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61639
--- Comment #1 from Alexander Pyhalov ---
LLVM developers confirmed the issue exists on OSX whith gcc 4.7.4 (but not
4.8/4.9).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61637
--- Comment #8 from Paolo Carlini ---
Something else besides AIX 7.1. Fore sure all the Linux targets are fine, for
example. This isn't a generic C++ front-end issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61637
--- Comment #7 from Krishnamoorthy C ---
Hi Paolo - S0orry , not in this case. The last few days were spent in playing
with the compiler options, but none seem to work. None of the throws are being
caught.
When you say certain exceptions work o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61637
Paolo Carlini changed:
What|Removed |Added
Status|WAITING |UNCONFIRMED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61635
--- Comment #5 from Andi Kleen ---
Also I forgot to state: the git tree above now has a workaround
(disabling LTO for that file). If you want to reproduce revert the latest
commit first.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61536
--- Comment #20 from paolo at gcc dot gnu.org ---
Author: paolo
Date: Sat Jun 28 15:53:30 2014
New Revision: 212104
URL: https://gcc.gnu.org/viewcvs?rev=212104&root=gcc&view=rev
Log:
2014-06-28 Paolo Carlini
Revert:
2014-06-18 Paolo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61639
Bug ID: 61639
Summary: GCC 4.7.4 can't longer compile clang
Product: gcc
Version: 4.7.4
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61635
--- Comment #4 from Andi Kleen ---
Yes it uses -fno-toplevel-reordering to avoid the problems with the initializer
reordering.
I tried some workarounds for this, but nothing worked so far. Likely would need
a noreorder attribute.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61536
--- Comment #19 from Paolo Carlini ---
As far as I can see the macros at the beginning of gnu.ver do not work as they
normally do in C/C++ code because __GXX_WEAK__ remains undefined. For now I'm
simply going to revert the whole thing, cleanup an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54742
Sebastian Pop changed:
What|Removed |Added
CC||spop at gcc dot gnu.org
--- Comment #37
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61637
--- Comment #5 from Krishnamoorthy C ---
// Throw and catch not working
#include
using namespace std;
int main () {
try
{
throw 20;
}
catch (int e)
{
cout << "This is not caught " << e << '\n';
}
catch (...)
{
cout << "This
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61637
--- Comment #4 from Krishnamoorthy C ---
The symptoms are as follows:
1. Any exception thrown ( whether a empty throw or a number or a class object )
never reaches the catch
this is happening across the code base, always, i.e. none of the catc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61637
--- Comment #3 from Krishnamoorthy C ---
Compiler options tried:
---
CC= gcc
CXX=g++
Compilation flags
SYSCXXFLAGS= -Dlinux -Dlinux_x86_64 -DLINUX_AMD64 -O1 -maix64 -fpermissive
-Wextra -Wuninitialized -Winit-self -Wwrite-st
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20585
Bug 20585 depends on bug 29383, which changed state.
Bug 29383 Summary: Fortran 2003/F95[TR15580:1999]: Floating point exception
(IEEE) support
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29383
What|Removed |A
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29383
Francois-Xavier Coudert changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60249
--- Comment #10 from Ed Smith-Rowland <3dw4rd at verizon dot net> ---
On 06/28/2014 10:03 AM, paolo.carlini at oracle dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60249
>
> --- Comment #8 from Paolo Carlini ---
> Thanks, but in g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61638
Bug ID: 61638
Summary: "warning: multi-line comment" unclear and has false
positives
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61637
--- Comment #2 from Daniel Krügler ---
As usual you need to provide a code example and the used compiler flags.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60249
--- Comment #9 from Ed Smith-Rowland <3dw4rd at verizon dot net> ---
On 06/28/2014 10:03 AM, paolo.carlini at oracle dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60249
>
> --- Comment #8 from Paolo Carlini ---
> Thanks, but in ge
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29383
--- Comment #15 from Francois-Xavier Coudert ---
Author: fxcoudert
Date: Sat Jun 28 14:17:41 2014
New Revision: 212102
URL: https://gcc.gnu.org/viewcvs?rev=212102&root=gcc&view=rev
Log:
PR fortran/29383
gcc/fortran/
* gfortran.h (gfc_si
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61637
Paolo Carlini changed:
What|Removed |Added
Severity|blocker |normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60249
--- Comment #8 from Paolo Carlini ---
Thanks, but in general I would recommend sending patches to gcc-patches in a
separate email, with a clear [C++ Patch] or something similar in the subject.
Also, please minimize jokes and other redundant conte
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61637
Paolo Carlini changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60249
--- Comment #6 from Ed Smith-Rowland <3dw4rd at verizon dot net> ---
On 06/27/2014 05:39 PM, paolo.carlini at oracle dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60249
>
> --- Comment #5 from Paolo Carlini ---
> Patch looks *grea
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60249
--- Comment #7 from Ed Smith-Rowland <3dw4rd at verizon dot net> ---
Created attachment 33026
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33026&action=edit
patch_from_hell
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61636
--- Comment #3 from tower120 ---
I found that as only I pass *this as parameter and then call functions from it,
it works ok. But it have to be auto:
/// This work
std::cout << if_else(do_first,
*this,
[&]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61637
Bug ID: 61637
Summary: C++ program does not catch exceptions on AIX 7.1
Product: gcc
Version: 4.8.1
Status: UNCONFIRMED
Severity: blocker
Priority: P3
Component
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60770
--- Comment #9 from Marc Glisse ---
The warnings are "normal", they also appear in a non-patched build, so that
leaves only the coalesce errors.
(In reply to Eric Botcazou from comment #8)
> The Ada front-end is the only serious user of abnormal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61536
--- Comment #18 from Paolo Carlini ---
In other terms, I don't see how !__GXX_TYPEINFO_EQUALITY_INLINE may end up
being true on x86_64-linux given the beginning of abi/pre/gnu.ver
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61536
--- Comment #17 from Paolo Carlini ---
It is not expected of course, but I'm traveling, I cannot look into it now, I
have no idea why is the symbol exported, is the macro we added for ARM
misbehaving somehow for Linux? I can't imagine how since t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60770
Eric Botcazou changed:
What|Removed |Added
CC||ebotcazou at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61536
--- Comment #16 from Marc Glisse ---
I am now getting an abi_check failure on x86_64-linux-gnu on a -O0 -g build
because of this symbol. Is it expected?
1 incompatible symbols
0
_ZNKSt9type_infoeqERKS_
std::type_info::operator==(std::type_info
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61530
Joost VandeVondele changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61636
Paolo Carlini changed:
What|Removed |Added
CC|tower120 at gmail dot com |adam at jessamine dot
co.uk
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61636
--- Comment #1 from tower120 ---
Furthermore, if not pass "data" as a lambda function param, but capture it from
current scope, it deduces type wrong.
http://coliru.stacked-crooked.com/a/ae022b9d25d93490
Uncomment static_cast to make it work.
B
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61636
Bug ID: 61636
Summary: generic lambda "cannot call member function without
object"
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58051
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58055
Bug 58055 depends on bug 58051, which changed state.
Bug 58051 Summary: [DR1579] No named return value optimization when returned
object is implicitly converted
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58051
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58051
--- Comment #4 from Jonathan Wakely ---
Author: redi
Date: Sat Jun 28 07:45:27 2014
New Revision: 212099
URL: https://gcc.gnu.org/viewcvs?rev=212099&root=gcc&view=rev
Log:
gcc/cp:
DR 1579
PR c++/58051
* typeck.c (check_return_expr):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61634
Markus Trippelsdorf changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60770
--- Comment #7 from Marc Glisse ---
Created attachment 33024
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33024&action=edit
replace clobber with default def
This passes bootstrap+testsuite with all default languages, but it breaks ada,
I
61 matches
Mail list logo
