https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110057
user202729 changed:
What|Removed |Added
CC||user202729 at protonmail dot
com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110057
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110057
--- Comment #10 from CVS Commits ---
The trunk branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:a47e615fbf9c6f4b24e5032df5d720b6bf9b63b5
commit r14-2853-ga47e615fbf9c6f4b24e5032df5d720b6bf9b63b5
Author: Ng YongXiang
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110057
--- Comment #9 from Ng YongXiang ---
Would anyone be willing to provide some feedback regarding the attachment
(https://gcc.gnu.org/bugzilla/attachment.cgi?id=55256=diff) that I have
created? Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110057
--- Comment #8 from Ng YongXiang ---
Just added a patch to illustrate the array destruction issue. What do you
think?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110057
Ng YongXiang changed:
What|Removed |Added
CC||yongxiangng at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110057
--- Comment #6 from Ng YongXiang ---
That is interesting. Thanks for the reply.
However, I'd argue that the 2 bugs mentioned are different from what I am
proposing. The 2 bugs linked access virtual functions via ptr (delete p;
val->f();) and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110057
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110057
--- Comment #4 from Ng YongXiang ---
Would anyone be able to direct me to which portion of the code is responsible
for this threshold between len 2 & 3 array? Is this the responsibility of the
c++ frontend? or is it still related to the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110057
--- Comment #3 from Ng YongXiang ---
I'm giving the example of an array for now, because gcc treatment of the
destructor is inconsistent and depends on the length of the array. Clang on the
other hand is able to devirtualize the destructor in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110057
--- Comment #2 from Andrew Pinski ---
I am not 100% sure the all of the objects in the vector has to be in type of
C. Because you could do some tricks dealing with inplacement new.
>if this applies to raw arrays
It does applies to raw arrays.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110057
--- Comment #1 from Andrew Pinski ---
I don't think it should be checking ssa dump (which is the output right after
going into ssa mode) but rather optimized.
12 matches
Mail list logo
