On 08/24/2010 07:38 PM, Basile Starynkevitch wrote:
> * what is the preferred way of obtaining a sequence of small patches?
> svn diff -x -p gives one big *.diff file! Should we split it by hand?
> Are there other tools producing a sequence of small patches?
http://savannah.nongnu.org/projects/qui
Suppose I have two insns, one reserving (A|B|C), and the other reserving
A. I'm observing that when the first one is scheduled in an otherwise
empty state, it reserves the A unit and blocks the second one from being
scheduled in the same cycle. This is a problem when there's an
anti-dependence of c
On 02/11/2011 02:13 PM, Alexander Monakov wrote:
> Could you please clarify a bit: would the modified behavior match what your
> target CPU does? The current behavior matches CPUs without lookahead in
> instruction dispatch: the first insn goes to the first matching execution
> unit (A), the secon
On 02/11/2011 07:43 PM, Frédéric RISS wrote:
> Le vendredi 11 février 2011 à 13:33 +0100, Bernd Schmidt a écrit :
>> Suppose I have two insns, one reserving (A|B|C), and the other reserving
>> A. I'm observing that when the first one is scheduled in an otherwise
>> empt
On 04/04/2011 11:58 PM, Steven Bosscher wrote:
> In the PR audit trail, I've proposed to revert the patch, and HJ and
> Benjamin are also in favor of that. In Benjamin's works: Bootstrap has
> been broken for much too long, on all the common devel arches.
Which is not actually true, see the secon
On 04/05/2011 12:51 AM, Ian Lance Taylor wrote:
> Steven Bosscher writes:
>
>> My proposal would be: A patch may be reverted immediately by anyone
>> with SVN write access if bootstrap is broken for more than 24 hours on
>> any primary target. With proper notification to everyone involved,
>> obv
On 04/05/2011 08:26 AM, Steven Bosscher wrote:
> On Tue, Apr 5, 2011 at 3:14 AM, Bernd Schmidt wrote:
>
>> For i686-linux bootstraps it's hard to argue against it, but in general
>> I find it easier to cope with the occasional broken tree than with
>> getting pa
On 04/05/2011 08:26 AM, Steven Bosscher wrote:
> I don't understand, really, why it's such a big deal to revert a patch
> quickly if it broke something.
To answer this as well, firstly a proposal that comes with a request to
revert the wrong patch discredits itself.
Breaking stuff by accident is
On 04/05/2011 02:23 PM, Steven Bosscher wrote:
> However, my point is that developers can investigate breakage without
> keeping the trunk broken.
If they can reproduce it; you don't always have access to the system
that shows the breakage. A reversion policy that's too trigger-happy can
leave yo
On 04/05/2011 04:49 PM, Jeff Law wrote:
> On 04/04/11 20:57, H.J. Lu wrote:
>> Patch was checked in at Fri Apr 1 17:46:17 2011. I reported the failure
>> at 2011-04-01 18:49:28 and identified the range of causes. It is too bad
>> to take 3 days to fix it.
> Note the checking was Friday evening,
On 05/05/2011 11:53 PM, Ian Lance Taylor wrote:
> Jon Grant writes:
>
>> Is it expected that more than one -o option should be allowed by GCC
>> on command line? The later -o option overriding earlier.
>
> Yes, this is expected. Most Unix utilities behave that way: when an
> option with an argu
ru
avr port Eric Weddington eric.wedding...@atmel.com
bfin port Bernd Schmidt ber...@codesourcery.com
bfin port Jie Zhang jzhang...@gmail.com
+c6x port Bernd Schmidt ber...@codesourcery.co
On 06/01/2011 04:00 PM, Georg-Johann Lay wrote:
> Eric Botcazou schrieb:
>>> You are right, I was staring at the wrong place. subreg of hardreg
>>> should not be there.
>>
>> You can take a look at PR target/48830, this is a related problem for the
>> SPARC where reload generates:
>>
>> (set (reg:
On 06/01/2011 05:35 PM, Georg-Johann Lay wrote:
> The reason for why a subreg of hardreg is there during reload is that
> on avr, r29:r28 is the frame pointer (word_mode is QI and Pmode is
> HI). Because in many places of the compiler, there are tests like "if
> (regno == FRAME_POINTER_REGNUM)", t
On 06/01/2011 06:06 PM, Georg-Johann Lay wrote:
> From the internals description, HARD_FRAME_POINTER_REGNUM appears to
> serve different purpose, and sources indicate that it is used similar,
> i.e. per regno == HARD_FRAME_POINTER_REGNUM instead if having a rtx or
> reg_class and test for overlaps
201 - 215 of 215 matches
Mail list logo
