Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: daniel.kruegler at googlemail dot com
gcc 4.9.0 20130922 (experimental) compiled with the flags
-std=c++11 -Wall -pedantic-errors
rejects the following code:
//-
struct
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58590
--- Comment #2 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Paolo Carlini from comment #1)
Not having investigated this issue at all, I doubt that it should be
considered a SFINAE proper issue,
Well, the actual
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58590
--- Comment #4 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Paolo Carlini from comment #3)
I still believe this isn't a SFINAE proper issue.
Could you please elaborate why?
Also note that in the original testcase
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58590
--- Comment #9 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Paolo Carlini from comment #5)
Because a SFINAE proper error is when you have an hard error, essentially by
definition from the implementation point
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58536
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58548
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58549
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58561
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58407
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58358
--- Comment #9 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Paolo Carlini from comment #8)
About the duplication, you may want to review what Francois posted to the
mailing list a few days ago and send your comments
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58352
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58352
--- Comment #3 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to 1zeeky from comment #2)
I am aware that the code is invalid; I'm not saying there shouldn't be an
error.
Then I was mislead by your comment: I'm not 100
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58352
--- Comment #4 from Daniel Krügler daniel.kruegler at googlemail dot com ---
Maybe related to bug 16564?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58353
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58338
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58265
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53025
--- Comment #3 from Daniel Krügler daniel.kruegler at googlemail dot com ---
This is just a polite reminder for some response. I'm especially interested to
hear whether there exist any reasonable doubts on the validity of the arguments
brought
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58191
--- Comment #3 from Daniel Krügler daniel.kruegler at googlemail dot com ---
First, this issue should be categorized as belonging to the component
libstdc++, not to c++.
Second, the defect report is invalid, because std::upper_bound requires
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58191
--- Comment #5 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Paolo Carlini from comment #2)
Francois, did we change anything in the library for 4.8.x?
I think that Francois added more iterator concept checking
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58184
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58181
--- Comment #3 from Daniel Krügler daniel.kruegler at googlemail dot com ---
My understanding is that the presented program has undefined behaviour and that
its assertion may fail or may not. The reason being that the outer lambda
expression has
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58083
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: daniel.kruegler at googlemail dot com
The following observations where originally found by testing the
std::is_trivial trait from type_traits, but the actual problem
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58046
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58062
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58063
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58063
--- Comment #3 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Paolo Carlini from comment #2)
I suppose a minimal reproducer could involve a file scope static of some
sort...
I'm a bit confused by your reply, Paolo
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58063
--- Comment #6 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Paolo Carlini from comment #5)
Ah, in case isn't obvious already: it only happens when the I/O expression
has the ! operator in front.
I suspected
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58063
--- Comment #8 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Paolo Carlini from comment #7)
But it happens with -O0 too, right?
Yes.
In any case we badly need a reduced testcase ;)
I agree. Unfortunately I'm
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58040
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57888
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57892
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
Severity: minor
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: daniel.kruegler at googlemail dot com
gcc 4.9.0 20130616 (experimental) diagnoses a warning for the following code
compiled with the flags:
-Wall
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49022
--- Comment #28 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Paolo Carlini from comment #27)
Yes.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57825
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57825
--- Comment #4 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Tomasz Kamiński from comment #2)
Propably this is also causing the problem with the standard library
is_function and is_member function traits, because
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57825
--- Comment #5 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Paolo Carlini from comment #3)
Daniel, which library testcases did we commit?!? ;) Crazy.
During an intermediate state we had bug 57388 which prevented
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57775
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57793
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57746
--- Comment #7 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Andy Lutomirski from comment #4)
Daniel, I'm unconvinced that your interpretation is the intended one.
Well, [temp.spec] p5 says more strongly
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57764
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57746
--- Comment #3 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Jonathan Wakely from comment #2)
It does for G++, it's been accepted as an extension in C++03 mode for years.
What I actually meant to say with my comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57746
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57632
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57614
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57626
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57610
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57599
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57588
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57588
--- Comment #5 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Jonathan Wakely from comment #2)
Although shouldn't it fail to compile, due to private destructor and copy
constructor?
I agree, it should fail
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57595
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57575
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57570
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57543
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57527
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57502
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57504
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57505
--- Comment #2 from Daniel Krügler daniel.kruegler at googlemail dot com ---
This is fixed in gcc 4.9 trunk and I believe it has already been fixed in gcc
4.8 due to bug #50043.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57484
--- Comment #4 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Charles L. Wilcox from comment #3)
Signaling NaN for type f in hex is 7fe0.
I agree, this one doesn't look right to me, because that looks indeed like
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57480
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57480
--- Comment #3 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Jonathan Wakely from comment #2)
My interprettaion is that the standard does not say anything about that (I
think I had once a similar question in regard
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57484
--- Comment #1 from Daniel Krügler daniel.kruegler at googlemail dot com ---
I haven't checked your bit arithmetics, but I have checked the full bit
patterns of the resulting NaNs in hex on my mingw-64 bit system. What I'm
getting
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57466
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: daniel.kruegler at googlemail dot com
gcc 4.9.0 20130519 (experimental) compiled with the flags
-std=c++11 -Wall -pedantic-errors
rejects the following code:
//
int get_int();
#define
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57437
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57444
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47765
--- Comment #8 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Paolo Carlini from comment #7)
Do we have a DR # for this issue?
It seems to me that this is
http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_active.html
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57388
--- Comment #3 from Daniel Krügler daniel.kruegler at googlemail dot com ---
Extending std::is_function in regard to ref-qualified functions will depend on
that issue. I haven't found a way to get around these ICEs in the (updated)
test cases.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52216
--- Comment #4 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Paolo Carlini from comment #3)
It seems that this is CWG 1465 and it will be resolved by
http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_active.html#1351
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52216
--- Comment #6 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Paolo Carlini from comment #5)
It would be great to have these test cases added.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57408
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57408
--- Comment #3 from Daniel Krügler daniel.kruegler at googlemail dot com ---
Further simplification down to a library-free test case:
//--
templatetypename Callable
struct Impl
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57416
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57416
--- Comment #4 from Daniel Krügler daniel.kruegler at googlemail dot com ---
If you remove the still existing member initializer in func1, does the ICE
still exist? (On 4.9 after removal of that initializer I could compile and run
the program
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57416
--- Comment #5 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Daniel Krügler from comment #4)
We had a clash here, but except for my first observation the remaining
questions are still relevant.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56991
--- Comment #4 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Matheus Izvekov from comment #2)
I get also a similar bug:
#include initializer_list
//is accepted by gcc
constexpr std::initializer_listint good1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57392
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57397
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57403
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: daniel.kruegler at googlemail dot com
When attempting to update the library test cases that use the test_category
template I stumbled across compiler error
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57406
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
Status|UNCONFIRMED
: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: daniel.kruegler at googlemail dot com
While attempting to upgrade std::function for functions with ref-qualifiers I
found that the following code gives an ICE for gcc 4.9.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57384
--- Comment #2 from Daniel Krügler daniel.kruegler at googlemail dot com ---
I have the impression that this *could* be related to
http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_active.html#1488
This is unchecked yet, because I'm leaving my
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57388
--- Comment #2 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Daniel Krügler from comment #0)
While attempting to upgrade std::function for functions with ref-qualifiers
[..]
Oops, I meant std::is_function of-course.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57248
--- Comment #3 from Daniel Krügler daniel.kruegler at googlemail dot com ---
The code looks valid to me. I think that Paolo just wanted to point out that
the library implementation does not cause this. I agree with him and can
confirm
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57335
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57314
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56976
--- Comment #3 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Akim Demaille from comment #2)
You are right, I misread your code example in the haste. I agree that this is
not related to CWG 1604 (we have no mixed case
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57270
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: daniel.kruegler at googlemail dot com
The following code is rejected if compiled with gcc 4.9.0 20130505
(experimental) using the flags
-std=c++11 -Wall -pedantic-errors
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57250
--- Comment #2 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Jonathan Wakely from comment #1)
Thanks for the pointer to the status page - sorry, I didn't check it before.
For the future: Does it make sense to open
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57253
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: daniel.kruegler at googlemail dot com
Consider this as a reminder bug entry to provide the atomic_* overloads for
std::shared_ptr. A minimal test case could be:
#include memory
int main() {
const std::shared_ptrint p
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57239
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54320
--- Comment #13 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Paolo Carlini from comment #10)
FWIW, I fully agree with Jason: VLAs are very restricted and don't even allow
for forming references to them, so
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57220
Bug #: 57220
Summary: [mingw] Undefined reference to __mingw_strtod
Classification: Unclassified
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57220
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
Keywords
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57220
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57220
--- Comment #5 from Daniel Krügler daniel.kruegler at googlemail dot com
2013-05-08 19:56:06 UTC ---
(In reply to comment #3)
Thanks for the litmus test, Kay. The result output I'm getting is:
MinGW-W64 Runtime 3.0 (alpha - rev. 0) -00-00
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57220
--- Comment #7 from Daniel Krügler daniel.kruegler at googlemail dot com
2013-05-08 20:25:44 UTC ---
(In reply to comment #6)
The attached '-v' '-save-temps' output indicates version 4.9.0 20130505
(experimental) (x86_64-w64-mingw32), but I'm
301 - 400 of 881 matches
Mail list logo