https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88499
--- Comment #3 from Teodor Petrov ---
@Marc Glisse: Would it be possible to give an explanation why this is not a
good idea? Link to some kind of a documentation which explains that this
behaviour is expected?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88499
--- Comment #1 from Teodor Petrov ---
Here are the commands used to reproduce the bug:
$ g++ -g -fPIC -Ofast -msse4.2 -std=c++11 -ffunction-sections -fdata-sections
-ffast-math -fvisibility=hidden -fexceptions -Wno-c++11-extensions
gcc_division.
: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: fuscated at gmail dot com
Target Milestone: ---
Created attachment 45237
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45237&acti
++
Assignee: unassigned at gcc dot gnu.org
Reporter: fuscated at gmail dot com
Target Milestone: ---
It happens with all versions I have access to (4.4.7, 4.8.x, 4.9.x, 5.3.0).
To reproduce:
> cat c++noreturn.cpp
int test() {}
int main() {
return 0;
}
> g++-5.3.0 c++noretu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63619
--- Comment #4 from Teodor Petrov ---
FYI: clang fixed the same issue by adding it to -Wdelete-incomplete
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63619
--- Comment #3 from Teodor Petrov ---
We already use -Werror=delete-incomplete, so it will be easier for us, because
it will just work.
But if you ask me (as a user) it is best to just change the standard to force
these two as errors. I know thi
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: fuscated at gmail dot com
Save this snippet in delete_void.cpp
int main() {
void *a=new char[100];
delete [] a;
return 0;
}
$ g++ -fdiagnostics-show-option delete_void.cpp
delete_void.cpp: In function ‘int
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58114
--- Comment #4 from Teodor Petrov ---
@Jonathan Wakely: Do you think the ISO C++ standard people will be willing to
change this behaviour for a future standard? I'm asking in order to know if
there is any point in starting a conversation with them
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58114
Teodor Petrov changed:
What|Removed |Added
CC||fuscated at gmail dot com
--- Comment #1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19165
--- Comment #17 from Teodor Petrov 2013-01-30
20:34:00 UTC ---
(In reply to comment #16)
>
> If you have some developer power to spare, it may be worthwhile to try to
> tackle this yourself. Otherwise I am afraid this will never be imple
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19165
Teodor Petrov changed:
What|Removed |Added
CC||fuscated at gmail dot com
trov
--
Summary: std::tr1::bind fails to compile with pointer to member
function
Product: gcc
Version: 4.3.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: fuscated at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38238
12 matches
Mail list logo
