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 ;
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
> > 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 09/13/2016 04:28 PM, Jeff Law wrote:
On 08/19/2016 08:58 AM, Aldy Hernandez wrote:
I'd just drop the /*strict_mode_p*/ comment in both places it appears in
your patch's change to passes.def. I think we've generally frowned on
those embedded comments, even though some have snuck in.
I've
This patch broke bootstrap on AIX.
In altivec_init_builtins(), the loop to initialize predicates is
encountering mode1 == SImode.
Thanks, David
Hi,
While computing jump function value range for pointer, I am wondering if
we can assume that any tree with ADDR_EXPR will be nonnull.
That is, in cases like:
int arr[10];
foo ([1]);
OR
struct st
{
int a;
int b;
};
struct st s2;
foo ();
Attached patch tries to do this. I am not sure
Hi Folks,
The attached patch does some minor cleanup and bumps the libgfortran version
number. I have wanted to reorder the dtp structure for many years now. Not
strictly needed but it has bugged me forever.
The bump is needed because of the significant changes from implementation of
DTIO.
101 - 107 of 107 matches
Mail list logo