https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68649
--- Comment #18 from Joost VandeVondele
---
since this PR, and the related PR77278 can presumably only be fixed by changing
libgfortran abi (at least if I understand Richard's suggestion for fixing
this). The announced major version bump of
This fixes the BB_VISITED bug in IRA I ran into earlier this year,
removing the superfluous clearing in VRP and the SSA propagator as well
as removing the now always true do_dce flag from substitute-and-fold.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77943
--- Comment #13 from Martin Liška ---
The replacement you described fully makes sense for me! As I mentioned earlier,
I'm not c++ expert, I can't come up with more possible counter examples that
worth for testing.
However, we'll fix further
On Mon, 17 Oct 2016, Andrew Pinski wrote:
> On Mon, Oct 17, 2016 at 5:26 AM, Richard Biener wrote:
> >
> > $subject, applied as obvious.
>
> I think you should do the same for the vectorizer too. I noticed that
> when testing the patch for loop splitting.
Can't see where
On Mon, 17 Oct 2016, Richard Biener wrote:
>
> This refactors propagation vs. substitution and handles condition
> simplification properly as well as passing a known taken edge down
> to the DOM walker (avoiding useless work and properly handling PHIs).
>
> If we do all the work it's stupid to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78015
Bug ID: 78015
Summary: pthread_cancel while some exception is pending results
in std::terminate ()
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity:
> > Ah, so you have
> >
> > foo () { loop }
> > main()
> > {
> > if ()
> >{
> > foo ();
> > exit (0);
> >}
> > ...
> > return 0;
> > }
> >
> > and foo is marked cold because its only call is on the path to exit (0)?
>
>
> Actually the case I have here is just:
> foo () {
On Mon, 17 Oct 2016, Richard Biener wrote:
>
> This fixes matching of toplevel (cond (lt @1 @2) ...) as reported by
> Bin to me privately.
>
> Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
This is what I applied.
Richard.
2016-10-18 Richard Biener
Hi,
this is a regression present on the mainline and 6 branch: the compiler now
generates wrong code for the attached testcase at -O because of an internal
conflict about boolean types. The sequence is as follows. In .mergephi3:
boolean _22;
p__enum res;
:
if (_22 != 0)
goto ;
201 - 209 of 209 matches
Mail list logo