Let me add to my own post saying that it seems that the problem is that the
list scheduler is greedy in the sense that it will take an instruction from the
ready list no matter what when waiting and trying to pair it with later on with
another instruction might be more beneficial. In a sense it
We will have a BOF on accelerators at GNU Tools Cauldron: Sunday July
14, 11:30am. Below is an abstract. If you have any comments in
advance, for example further suggestions about what to discuss at his
BOF or at Cauldron, please let me know.
In this BOF, we will discuss how we can support acce
Hi,
I have noticed an interesting behaviour based on the memset builtin test on
4.8.1. If you compile memset-lib.i with -O3 you get an infinite recursion.
$ cat memset-lib.i
# 1
"/home/pmatos/work/fp_gcc-25x/gcc/testsuite/gcc.c-torture/execute/builtins/memset-lib.c"
# 1 ""
# 1
"/home/pmatos/wor
> -Original Message-
> From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of Paulo
> Matos
> Sent: 27 June 2013 14:52
> To: gcc@gcc.gnu.org
> Subject: Infinite recursion due to builtin pattern detection
>
> Another thing I cannot grasp is that the test for inside_main c
> -Original Message-
> From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of Paulo
> Matos
> Sent: 27 June 2013 15:02
> To: gcc@gcc.gnu.org
> Subject: RE: Infinite recursion due to builtin pattern detection
>
>
> Let me add that one of the replies to this last issue wou
On Wed, 26 Jun 2013, David Malcolm wrote:
> FWIW I wonder to what extent the discussions that follow all exhibit a
> tradeoff between the desire to provide a clean API vs the desire to
> minimize the size of the patch (to reduce backporting pain).
I don't think reducing backporting pain is partic
Paulo Matos writes:
> That explains why GCC removes the condition but the main issue of the memset
> recursion still stands.
Known problem. See GCC PR56888.
On 27/06/2013 16:02, Mikael Pettersson wrote:
Paulo Matos writes:
That explains why GCC removes the condition but the main issue of the memset
recursion still stands.
Known problem. See GCC PR56888.
Thanks for the reference Mikael, that's exactly it.
--
Paulo Matos
On Thu, 2013-06-27 at 14:50 +, Joseph S. Myers wrote:
> On Wed, 26 Jun 2013, David Malcolm wrote:
>
> > FWIW I wonder to what extent the discussions that follow all exhibit a
> > tradeoff between the desire to provide a clean API vs the desire to
> > minimize the size of the patch (to reduce b
On Thu, 27 Jun 2013, David Malcolm wrote:
> I want to focus on "removal of global state", and I want that to be
> separate from "cleanups of internal APIs".
Whereas I'm thinking of global state as being a symptom of a problem -
messy interfaces that have accreted over time - rather than the prob
An update on this year's Cauldron.
The presentation abstracts are now available at
http://gcc.gnu.org/wiki/cauldron2013
If you do not see yours, please send it to
tools-cauldron-ad...@googlegroups.com.
Diego.
June's release of http://www.SportsBeat.com will shift athletes, coaches and
parents away from old school and socially inept Team Management websites like
Eteamz, TeamSnap and Shutterfly.
SportsBeat brings a completely free advanced media tool that allows its users
to manage all of their teams,
12 matches
Mail list logo