http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60536
--- Comment #3 from Markus Trippelsdorf ---
(In reply to Kostya Serebryany from comment #2)
> Please symbolize the output.
How?
asan_symbolize.py doesn't parse this output.
If I run addr2line on the first few symbols by hand I get:
Stack:
siga
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60536
--- Comment #4 from Andrew Pinski ---
(In reply to Markus Trippelsdorf from comment #3)
> (In reply to Kostya Serebryany from comment #2)
> > Please symbolize the output.
>
> How?
> asan_symbolize.py doesn't parse this output.
> If I run addr2li
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60536
--- Comment #5 from Kostya Serebryany ---
> Clang trunk cannot build Firefox with -fsanitize=address, because I get
> asan related linker errors.
To the best of my knowledge, firefox is routinely built by several different
teams using clang+asan.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60536
--- Comment #6 from Kostya Serebryany ---
> _Unwind_Find_FDE+0x01D9 /home/markus/gcc/libgcc/unwind-dw2-fde-dip.c:462
> /home/markus/gcc/libgcc/unwind-dw2.c:1182
> _Unwind_Backtrace+0x004B /home/markus/gcc/libgcc/unwind.inc:291
Interestin
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60536
--- Comment #7 from Markus Trippelsdorf ---
(In reply to Kostya Serebryany from comment #5)
> > Clang trunk cannot build Firefox with -fsanitize=address, because I get
> > asan related linker errors.
> To the best of my knowledge, firefox is routi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60546
--- Comment #1 from Andrew Pinski ---
-fno-strict-aliasing fixes the issue So there might be an aliasing issue in the
code.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60536
--- Comment #8 from Markus Trippelsdorf ---
(In reply to Kostya Serebryany from comment #5)
> > Clang trunk cannot build Firefox with -fsanitize=address, because I get
> > asan related linker errors.
> To the best of my knowledge, firefox is routi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60050
Kai Tietz changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60244
Kai Tietz changed:
What|Removed |Added
CC||ktietz at gcc dot gnu.org
--- Comment #1 from
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60547
Bug ID: 60547
Summary: libcilkrts/runtime/record-replay.cpp: 2 * possible
problems in calls to scanf ?
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60548
Bug ID: 60548
Summary: [libvtv/scripts/sum-vtv-counts.c:108]: (warning) scanf
without field width limit s can crash with huge input
data.
Product: gcc
Version: 4.9
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60536
--- Comment #9 from Markus Trippelsdorf ---
(In reply to Kostya Serebryany from comment #6)
> > _Unwind_Find_FDE+0x01D9 /home/markus/gcc/libgcc/unwind-dw2-fde-dip.c:462
> > /home/markus/gcc/libgcc/unwind-dw2.c:1182
> > _Unwind_Backtrace+0x
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60548
David Binderman changed:
What|Removed |Added
Severity|normal |minor
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60547
David Binderman changed:
What|Removed |Added
Severity|normal |minor
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60534
Marek Polacek changed:
What|Removed |Added
Priority|P3 |P2
Status|UNCONFIRMED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60534
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60516
--- Comment #7 from Kai Tietz ---
Thanks for the patch. I am about to do a full-regression test for it. This
will take some time.
Quick test has shown that issue isn't 'thiscall' specific at all. stdcall, and
fastcall calling-convention do have
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60548
--- Comment #1 from Andrew Pinski ---
This file is never compiled so it is very minor.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60547
--- Comment #1 from Andrew Pinski ---
This code is never used unless you turn on the code manually.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60429
--- Comment #26 from rguenther at suse dot de ---
On Sat, 15 Mar 2014, linux at carewolf dot com wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60429
>
> --- Comment #25 from Allan Jensen ---
> Will it be backported to 4.8?
Yes.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60546
--- Comment #2 from Andrew Pinski ---
But it might be related to bug 60429.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60536
--- Comment #10 from Kostya Serebryany ---
> ==10632==ERROR: AddressSanitizer: heap-use-after-free on address
> 0x6021ec50 at pc 0x7f3e30645dbd bp 0x7fff6d3b2a60 sp 0x7fff6d3b2a38
> READ of size 2 at 0x6021ec50 thread T0
> #0 0x7f3e30
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60536
--- Comment #11 from Kostya Serebryany ---
> Sorry, but I don't have a google account and refuse to create one.
You can login to our bug tracker with any existing e-mail,
or you can contact us via address-saniti...@googlegroups.com
or you can fil
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60504
--- Comment #7 from Mikael Pettersson ---
(In reply to Bernd Edlinger from comment #6)
> that would be r208419 and r208150
Reverting r208150 + r208419 and rebuilding from scratch eliminated all acats
regressions.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60536
--- Comment #12 from Markus Trippelsdorf ---
(In reply to Kostya Serebryany from comment #11)
> > Sorry, but I don't have a google account and refuse to create one.
> You can login to our bug tracker with any existing e-mail,
> or you can contact
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60549
Bug ID: 60549
Summary: [4.9 Regression] Run time doubled for fatigue.f90 due
to SAVE changes
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Keywords: missed-opt
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60549
Tobias Burnus changed:
What|Removed |Added
CC||dominiq at lps dot ens.fr,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60536
--- Comment #13 from Kostya Serebryany ---
> What about the "allocating memory until the OOM killer hits" issue?
> Do you think this is an asan bug?
Dunno. File a bug with more details if you think it's a bug.
I guess you can close this one.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60534
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #2 f
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53513
--- Comment #7 from Oleg Endo ---
(In reply to Rich Felker from comment #6)
> On Sun, Mar 16, 2014 at 11:32:21PM +, olegendo at gcc dot gnu.org wrote:
> > If it's OK for a temporary mode switch to clobber other FPSCR bits (such as
> > in
> >
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60516
Jakub Jelinek changed:
What|Removed |Added
Attachment #32367|0 |1
is obsolete|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60549
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60549
--- Comment #2 from Richard Biener ---
Indeed once such variables have their address taken (trivially happens in
fortran) we have a hard time disambiguating them. You might want to try
(the imperfect) -fipa-pta, even though that pessimizes code i
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60536
Markus Trippelsdorf changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58851
--- Comment #14 from Andreas Schwab ---
Author: schwab
Date: Mon Mar 17 09:23:15 2014
New Revision: 208612
URL: http://gcc.gnu.org/viewcvs?rev=208612&root=gcc&view=rev
Log:
PR testsuite/58851
* gfortran.dg/unlimited_polymorphic_13.f90: Properly c
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58793
Bug 58793 depends on bug 58851, which changed state.
Bug 58851 Summary: FAIL: gfortran.dg/unlimited_polymorphic_13.f90 -O0
execution test
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58851
What|Removed |Added
-
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58851
Andreas Schwab changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60549
--- Comment #3 from Dominique d'Humieres ---
> You might want to try (the imperfect) -fipa-pta, even though that pessimizes
> code in some cases.
It does not change the run time for fatigue.f90.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60549
--- Comment #4 from Jakub Jelinek ---
(In reply to Dominique d'Humieres from comment #3)
> > You might want to try (the imperfect) -fipa-pta, even though that
> > pessimizes
> > code in some cases.
>
> It does not change the run time for fatig
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60536
--- Comment #15 from Jakub Jelinek ---
Well, even when it is Firefox/whatever bug, the question is why do you get a
crash in libgcc_s.so.1.
Is that because your libgcc is too old to handle the gcc 4.9 emitted unwind
info?
Note, I'm not aware of an
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60546
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
Su
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60536
--- Comment #16 from Markus Trippelsdorf ---
(In reply to Jakub Jelinek from comment #15)
> Well, even when it is Firefox/whatever bug, the question is why do you get a
> crash in libgcc_s.so.1.
> Is that because your libgcc is too old to handle t
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60537
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60535
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |4.9.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57425
--- Comment #18 from Mikael Pettersson ---
Bill, the backport patch has now been approved:
http://gcc.gnu.org/ml/gcc-patches/2014-03/msg00792.html
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60550
Bug ID: 60550
Summary: ICE on factory design pattern
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
As
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60551
Bug ID: 60551
Summary: __attribute__((used)) is ignored for 'static' function
declarations
Product: gcc
Version: 4.8.2
Status: UNCONFIRMED
Severity: normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60546
--- Comment #4 from Richard Biener ---
Created attachment 32370
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32370&action=edit
patch to fix store motion issue
Fixing that doesn't fix it (or my fix doesn't work ;)).
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60539
chrbr at gcc dot gnu.org changed:
What|Removed |Added
CC||chrbr at gcc dot gnu.org
--- Co
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53313
Sergei Trofimovich changed:
What|Removed |Added
CC||slyfox at inbox dot ru
--- Comment #
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60546
--- Comment #5 from linzj ---
Well,valgind do detect invalid memory usage.That's not an asan problem then.
Since it effects from 4.8,does that mean 4.8 is not secure any more?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39612
--- Comment #21 from Richard Biener ---
Created attachment 32371
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32371&action=edit
Fix
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39612
--- Comment #22 from Richard Biener ---
The fix uses the store-data-race avoiding path which keeps a flag per moved
mem-ref whether it was stored to. With that I can avoid loading from the ref
before the loop if there are no loads in the loop its
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39612
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60539
--- Comment #2 from chrbr at gcc dot gnu.org ---
note also that instead of merging the 3 max remaining bytes after the
world-at-time loop with the byte-at-a-time loop I had a version that unrolled
the 3 of them of we have 2 different path (word,byt
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60535
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60535
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment #
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60552
Bug ID: 60552
Summary: integer operation result is out of range ?
-__gnu_cxx::__numeric_traits<_ValueT>::__min^
Product: gcc
Version: 4.4.3
Status: UNCONFIRME
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60549
--- Comment #5 from Dominique d'Humieres ---
> And what exact change do you get with a mere
> http://gcc.gnu.org/ml/gcc-patches/2014-03/msg00754.html
> patch, against same version without it (e.g. both without the SAVE
> for MAIN__ change, or bot
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60516
--- Comment #9 from Kai Tietz ---
Did regression-test for 32-bit mingw for C, C++, and Fortran. No new
regressions occurred.
So patch is from my POV ok for trunk and branches
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60549
--- Comment #6 from Jakub Jelinek ---
(In reply to Dominique d'Humieres from comment #5)
> > And what exact change do you get with a mere
> > http://gcc.gnu.org/ml/gcc-patches/2014-03/msg00754.html
> > patch, against same version without it (e.g.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60552
Jonathan Wakely changed:
What|Removed |Added
Severity|major |normal
--- Comment #1 from Jonathan Wak
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60546
--- Comment #6 from Richard Biener ---
Meanwhile -fno-tree-dse also "fixes" this but it only prevents mayhem
downstream
(Jakub bisected this to a revision that exposed the issue, r158047). You have
to disable both tree DSE passes btw, thus it poi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53513
chrbr at gcc dot gnu.org changed:
What|Removed |Added
CC||chrbr at gcc dot gnu.org
--- Co
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60546
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60552
Sivaprasad changed:
What|Removed |Added
Severity|normal |major
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60552
--- Comment #2 from Sivaprasad ---
with GCC 4.6.3 also, we are facing same problems.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60040
Jorn Wolfgang Rennecke changed:
What|Removed |Added
CC||amylaar at gcc dot gnu.org
--- C
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60546
--- Comment #8 from linzj ---
I don't think it can be mark as resolved-invalid that fast.This code is used by
WebKit for a long time and no one would say this is an illegal algorithm.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60546
--- Comment #9 from linzj ---
If this is an illegal expression, it should be reported at compile time,not
generating a wrong code.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60535
Markus Trippelsdorf changed:
What|Removed |Added
Summary|[4.9 Regression] Link |Link failure with -flto and
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60429
--- Comment #27 from Richard Biener ---
Author: rguenth
Date: Mon Mar 17 13:08:41 2014
New Revision: 208615
URL: http://gcc.gnu.org/viewcvs?rev=208615&root=gcc&view=rev
Log:
2014-03-17 Richard Biener
Backport from mainline
2014-03-11
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60485
--- Comment #4 from Richard Biener ---
Author: rguenth
Date: Mon Mar 17 13:08:41 2014
New Revision: 208615
URL: http://gcc.gnu.org/viewcvs?rev=208615&root=gcc&view=rev
Log:
2014-03-17 Richard Biener
Backport from mainline
2014-03-11
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60429
Richard Biener changed:
What|Removed |Added
Known to work||4.8.3, 4.9.0
Summary|[4.7/4.8
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60552
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60546
linzj changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60546
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53513
--- Comment #9 from Kazumoto Kojima ---
Although it seems that (1)-(5) in #3 are interesting points, they
are almost optimizations. I guess that programs with frequent FP
mode switchings are simply rare in real world and would be a bit
special or
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60535
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60535
--- Comment #4 from Richard Biener ---
(In reply to Jakub Jelinek from comment #3)
> Created attachment 32373 [details]
> gcc49-pr60535.patch
>
> Untested fix.
>
> There are 3 remaining tests I haven't removed the dg-skip-if for yet:
> c-c++-com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60534
--- Comment #3 from Marek Polacek ---
Author: mpolacek
Date: Mon Mar 17 14:15:51 2014
New Revision: 208616
URL: http://gcc.gnu.org/viewcvs?rev=208616&root=gcc&view=rev
Log:
PR middle-end/60534
* omp-low.c (omp_max_vf): Treat -fno-tree-loo
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60534
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53513
--- Comment #10 from Oleg Endo ---
(In reply to Kazumoto Kojima from comment #9)
> Although it seems that (1)-(5) in #3 are interesting points, they
> are almost optimizations.
Yep. Those are not necessary to get the functionality (of not usin
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60546
--- Comment #12 from linzj ---
Alright,should I change the algorithm to avoid this bug?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60546
--- Comment #13 from rguenther at suse dot de ---
On Mon, 17 Mar 2014, manjian2006 at gmail dot com wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60546
>
> --- Comment #12 from linzj ---
> Alright,should I change the algorithm to avoid t
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60546
--- Comment #14 from linzj ---
Well,but I have not figured out what goes wrong in the hashing algorithm. Would
you point it out.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60535
--- Comment #5 from Marek Polacek ---
(In reply to Jakub Jelinek from comment #3)
> g++.dg/ubsan/pr59437.C
>
> This one shows a bug either in the -fvtable-* verification stuff, or in
> cgraph, but doesn't look related to ubsan:
>
> ==27993== In
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59441
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57303
--- Comment #11 from Richard Biener ---
Author: rguenth
Date: Mon Mar 17 14:38:55 2014
New Revision: 208618
URL: http://gcc.gnu.org/viewcvs?rev=208618&root=gcc&view=rev
Log:
2014-03-17 Richard Biener
Backport from mainline
2013-05-21
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59139
--- Comment #7 from Richard Biener ---
Author: rguenth
Date: Mon Mar 17 14:38:55 2014
New Revision: 208618
URL: http://gcc.gnu.org/viewcvs?rev=208618&root=gcc&view=rev
Log:
2014-03-17 Richard Biener
Backport from mainline
2013-05-21
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60183
--- Comment #9 from Richard Biener ---
Author: rguenth
Date: Mon Mar 17 14:38:55 2014
New Revision: 208618
URL: http://gcc.gnu.org/viewcvs?rev=208618&root=gcc&view=rev
Log:
2014-03-17 Richard Biener
Backport from mainline
2013-05-21
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60183
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60546
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment #
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57303
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59139
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60546
--- Comment #16 from linzj ---
Yes,that may work.But what exactly go wrong in the original algorithm? I can't
change a correct algorithm just because it volatiles TBBA and make the compiler
generate wrong code.Because it's CORRECT logically.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59571
--- Comment #2 from paolo at gcc dot gnu.org ---
Author: paolo
Date: Mon Mar 17 14:53:05 2014
New Revision: 208619
URL: http://gcc.gnu.org/viewcvs?rev=208619&root=gcc&view=rev
Log:
/cp
2014-03-17 Paolo Carlini
PR c++/59571
* typeck2.c
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60553
Bug ID: 60553
Summary: segfault in gt_ggc_mx_lang_tree_node in Chromium with
LTO
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Prior
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59571
Paolo Carlini changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53513
--- Comment #11 from chrbr at gcc dot gnu.org ---
(In reply to Oleg Endo from comment #10)
> (In reply to Kazumoto Kojima from comment #9)
> > Although it seems that (1)-(5) in #3 are interesting points, they
> > are almost optimizations.
>
> Ye
1 - 100 of 166 matches
Mail list logo