On Mon, Mar 28, 2016 at 07:38:46PM -0500, Bill Schmidt wrote:
> For a long time we've had hundreds of failing guality tests. These
> failures don't seem to have any correlation with gdb functionality for
> POWER, which is working fine. At this point the value of these tests to
> us seems question
On Mon, Mar 28, 2016 at 07:57:54PM -0700, Richard Henderson wrote:
> The ICE comes fixing up a debug_insn, and the debug info incoming to the
> pass seems reasonable. Just recognizing that this situation is possible and
> not asserting appears to work.
>
> Ok?
>
>
> r~
> * lower-subreg.c
The ICE comes fixing up a debug_insn, and the debug info incoming to the pass
seems reasonable. Just recognizing that this situation is possible and not
asserting appears to work.
Ok?
r~
* lower-subreg.c (simplify_subreg_concatn): Reject paradoxical subregs.
diff --git a/gcc/lower-
On Mar 28, 2016, at 5:38 PM, Bill Schmidt wrote:
> For a long time we've had hundreds of failing guality tests. These
> failures don't seem to have any correlation with gdb functionality for
> POWER, which is working fine.
> Verified to remove hundreds of failure messages on
> powerpc64le-unknow
On 25/03/16 08:02, Charles Baylis wrote:
> When compiling with -mlong-calls and -pg, calls to the __gnu_mcount_nc
> function are not generated as long calls.
>
> This is the sequel to this patch
> https://gcc.gnu.org/ml/gcc-patches/2016-02/msg00881.html
>
> This patch fixes the following pr
The attached patches add an "-mnodiv" option to FT32, preventing use of the
divide and modulo instructions. This required additional software div/mod
implemtations in FT32's libgcc.
2016-03-28 James Bowman
* config/ft32/ft32.opt (mnodiv): New.
* config/ft32/ft32.md (*divsi3,
Hi,
For a long time we've had hundreds of failing guality tests. These
failures don't seem to have any correlation with gdb functionality for
POWER, which is working fine. At this point the value of these tests to
us seems questionable. Fixing these is such low priority that it is
unlikely we w
Amazingly enough, my patch worked well enough that my NetBSD VAX kernel built
with GCC 5.3 is no longer crashing. I feel pretty good about what I have so far
so here's the complete diff for both the C++ exception fix and the bad
condition codes optimizer bug. It should be good enough to check in
An updated patch that resolves the issues with thumb2 support and adds
test cases as requested. Looking to check this into GCC 7 stage1 when it
opens.
2016-02-24 Michael Collison
* config/arm/arm-modes.def: Add new condition code mode CC_V
to represent the overflow bit.
* config
I have some bad news and some good news. The bad news is that there has been a
nasty optimizer bug lurking in the VAX backend for GCC for many years, which
has to do with over-optimistic removal of necessary tst/cmp instructions under
certain circumstances. This manifests at -O or higher and the
I think let's defer the fix for c++/60760 (i.e. the nullptr_p bits)
until stage 1, when it can be combined with the POINTER_PLUS_EXPR fix,
and put the rest of this patch in now.
I can split up the patch into two and post the subset without
the fix for c++/60760, though I don't expect to be done
The constexpr evaluation code uses the inlining code to remap the
constexpr function body for evaluation so that recursion works properly.
In this testcase __func__ is declared as a static local variable, so
rather than remap it, remap_decls tries to add it to the local_decls
list for the func
Sorry, Should have replied to gcc-patches list.
Thanks,
bin
-- Forwarded message --
From: "Bin.Cheng"
Date: Tue, 29 Mar 2016 03:55:04 +0800
Subject: Re: [PATCH PR69489/01]Improve tree ifcvt by storing/tracking
DR against its innermost loop bahavior if possible
To: Richard Biener
(Ping and changelog fix)
On Tue, Mar 22, 2016 at 11:15 AM, Marcos Díaz
wrote:
> Hi,
>the attached patch adds a new attribute 'security_sensitive' for functions.
> The idea was discussed in PR middle-end/69976.
> This attribute makes gcc to emit clean up code at the function's epilogue.
> This
On 03/23/2016 09:10 PM, Alan Modra wrote:
On Wed, Mar 23, 2016 at 05:04:39PM +0100, Olivier Hainque wrote:
The reason why 894 is not accounted in the base ref computation is because it
is part of the epilogue sequence, and init_alias_analysis has:
/* Walk the insns adding values to the n
Hi Thomas!
Do you plan to commit this patch? :)
On Mon, Sep 29, 2014 at 09:24:40 -0600, Jeff Law wrote:
> On 09/29/14 08:26, Thomas Schwinge wrote:
> >On Mon, 29 Sep 2014 13:58:31 +, "Tannenbaum, Barry M"
> > wrote:
> >>In a nutshell, add the following code to main() before the call to f3():
Hi Paul,
thanks for the quick review. Committed to gcc-5-branch as r234507. The
patch for trunk needs more polishing than expected. I hope to present
it soon.
Regards,
Andre
On Sun, 27 Mar 2016 19:19:11 +0200
Paul Richard Thomas wrote:
> Hi Andre,
>
> The patch looks to be fine to me
> Le 28 mars 2016 à 15:11, Jason Merrill a écrit :
>
> On 03/28/2016 09:02 AM, Dominique d'Humières wrote:
>>
>>> Le 28 mars 2016 à 14:55, Jason Merrill a écrit :
>>>
>>> OK, thanks.
>>>
>>> Jason
>>
>> Does it mean that I should commit the patch?
>
> Please.
Revision 234504.
Dominique
On 03/28/2016 09:02 AM, Dominique d'Humières wrote:
Le 28 mars 2016 à 14:55, Jason Merrill a écrit :
OK, thanks.
Jason
Does it mean that I should commit the patch?
Please.
Jason
> Le 28 mars 2016 à 14:55, Jason Merrill a écrit :
>
> OK, thanks.
>
> Jason
Does it mean that I should commit the patch?
Dominique
OK, thanks.
Jason
Hi,
as described in the tracker we have bootstrap problems with in-tree gmp-6.1.0
on certain targets, and also a linker issue with check-mpc due to the changed
mpfr library path.
These are triggered by overriding CFLAGS and LDFLAGS in in-tree builds.
It did not happen with the gmp/mpfr/mpc versi
Thanks for the quick feedback.
The patch has been committed on trunk as rev. 234502 and on
gcc-5-branch as rev. 234503 .
In attachment three simple test cases; coarray_stop_str.f90 fails
because of a syntax error in the check string.
I guess the problem is due to the presence of the "STOPPED" str
On Mon, Mar 28, 2016 at 12:45:03PM +0200, Olivier Hainque wrote:
> > The normal -m32 compiler here generates code like
> >
> > lwz 11,0(1)
> >
> > and try as I might I cannot get it to fail. Maybe because the GPR11
> > setup here involves a load?
>
> You need to have had r11 last used to de
> On Mar 28, 2016, at 05:01 , Segher Boessenkool
> wrote:
>
> The normal -m32 compiler here generates code like
>
> lwz 11,0(1)
>
> and try as I might I cannot get it to fail. Maybe because the GPR11
> setup here involves a load?
You need to have had r11 last used to designate a globa
Hi Jakub, there's a path for deadlock on acc_device_lock when going
through the acc_set_device_type() OpenACC library function.
Basically, the gomp_init_targets_once() function should not be
called with that held. The attached patch moves it appropriately.
Also in this patch, there are several cas
Hi Bernd: I submitted the filled disclaimer form on March 4th. Now, a
representative of FSF mentioned that the copyright assignment is ready on their
end.
Can someone please go ahead and review the patch?
Best regards,
- Marcel
> On 4 Mar 2016, at 1:43 AM, Bernd Schmidt wrote:
>
> On 03/03/
27 matches
Mail list logo
