Hi Richard,
I have several patches that I've emailed to gcc-patches (some a few
days ago, some a bit longer). They are still pending code review.
Will this still be able to make it into gcc 4.5? The list of patches
is as follows:
http://gcc.gnu.org/ml/gcc-patches/2009-09/msg01170.html
http://gc
On Wed, Sep 30, 2009 at 10:49:40AM +0200, Richard Guenther wrote:
> >
> > Now, submitting a one liner as your first atte...@a new pass today
> > and then claiming the rest are just fixes, would be a stretch :-), but
> > for a patch like yours it does not seem unreasonable.
>
> Just to followup on
On Wed, 30 Sep 2009, Gerald Pfeifer wrote:
> On Tue, 29 Sep 2009, Dave Korn wrote:
> > We have ~48 hours left for stage 1 and I can't be confident of getting
> > it reviewed in the remaining time, so I'd like to make a special
> > request: can you, as RM, please say that this is OK in principle
On Tue, 29 Sep 2009, Dave Korn wrote:
> We have ~48 hours left for stage 1 and I can't be confident of getting
> it reviewed in the remaining time, so I'd like to make a special
> request: can you, as RM, please say that this is OK in principle and
> that if I can get v3 approval (it already has
Richard Guenther wrote:
> Status
> ==
>
> The trunk is in Stage 1. Stage 1 will end on Sep 30th.
Richard, I've got a patch for adding what I think (but may be wrong) counts
as a new feature - shared library libstdc++ as DLLs on windows platforms - and
it's been stuck in review limbo for tw
Hi,
I have a zero-extension elimination patch that has been reviewed and needs
one minor fix before it is ready for submission. I can get this in by Thursday,
October 1st. Would it be alright to submit this patch then ?
Thanks,
-Sriraman.
On Sat, Sep 19, 2009 at 1:57 PM, Richard Guenther
On Thu, 24 Sep 2009, Jason Merrill wrote:
> On 09/20/2009 08:07 AM, Dave Korn wrote:
> > Richard Guenther wrote:
> > > On Sun, 20 Sep 2009, Dave Korn wrote:
> >
> > > >BTW, why don't we call this more-flexible-stage-3 "stage 2" any more?
> > > > It
> > > > sounds a lot like the way that's sti
On 09/20/2009 08:07 AM, Dave Korn wrote:
Richard Guenther wrote:
On Sun, 20 Sep 2009, Dave Korn wrote:
BTW, why don't we call this more-flexible-stage-3 "stage 2" any more? It
sounds a lot like the way that's still described on develop.html.
Because "New functionality may not be introdu
> extensibility, this isn't a problem for these extensions, as older
> DWARF readers will simply ignore the location expressions that use the
> extensions -- which produces the same behavior as DWARF-2 without
> those extensions.
I said "will simply ignore" when I guess I should have said "should
> Are you saying that current gcc trunk should require -gdwarf-4
> to issue dwarf4 commands? I ask because r151815...
>
> http://gcc.gnu.org/ml/gcc-patches/2009-09/msg00220.html
>
> causes dwarf4 by default. Is there a consistent policy on this?
> Currently in PR41405, there is a proposal for a -
On Mon, Sep 21, 2009 at 11:23:11AM -0700, Cary Coutant wrote:
> >> So aren't we now likely to lose the first few days of what little
> >> remains of
> >> stage 1 waiting for trunk to start working again, then have a mad rush of
> >> people falling all over each other to get their new features in
>> So aren't we now likely to lose the first few days of what little remains
>> of
>> stage 1 waiting for trunk to start working again, then have a mad rush of
>> people falling all over each other to get their new features in in the last
>> couple of days? One of which will inevitably break tr
Richard Guenther wrote:
> On Sun, 20 Sep 2009, Dave Korn wrote:
>> BTW, why don't we call this more-flexible-stage-3 "stage 2" any more? It
>> sounds a lot like the way that's still described on develop.html.
>
> Because "New functionality may not be introduced during this period." is
> still
On Sun, 20 Sep 2009, Dave Korn wrote:
> Richard Guenther wrote:
>
> > Note that Stage 3 isn't that strict as it may sound. Maintainers have
> > quite amount of flexibility deciding what is considered a bug and thus
> > a bugfix during Stage 3 (note that Stage3 is _not_ only for regression
> > fi
Richard Guenther wrote:
> Note that Stage 3 isn't that strict as it may sound. Maintainers have
> quite amount of flexibility deciding what is considered a bug and thus
> a bugfix during Stage 3 (note that Stage3 is _not_ only for regression
> fixes). This includes obviously Graphite and LTO as
On Sun, 20 Sep 2009, Dave Korn wrote:
> Richard Guenther wrote:
>
> > The trunk is in Stage 1. Stage 1 will end on Sep 30th. After Stage 1
> > Stage 3 follows with only bugfixes and no new features allowed.
> > Stage 3 will end Nov 30th.
I'll answer your and Jacks question together.
> I do
Richard Guenther wrote:
> The trunk is in Stage 1. Stage 1 will end on Sep 30th. After Stage 1
> Stage 3 follows with only bugfixes and no new features allowed.
> Stage 3 will end Nov 30th.
I don't think this is the best time to do that. Trunk's been broken most of
last week and will probab
On Sep 19, 2009, at 18:02, Steven Bosscher wrote:
* GDB test suite should pass with -O1
Apparently, the current GDB test suite can only work at -O0,
because code reorganization messes up the scripting.
-Geert
On Sat, Sep 19, 2009 at 10:57:38PM +0200, Richard Guenther wrote:
>
> We've been accumulating quite a number of P1 bugs. Entering Stage 3
> should allow to improve considerably here in a short time.
>
Richard,
Will the graphite code be under strict stage 3 rules or will it
have more leeway u
On Sun, 20 Sep 2009, Steven Bosscher wrote:
> On Sat, Sep 19, 2009 at 10:57 PM, Richard Guenther wrote:
> > Since the last status report we have merged the VTA branch and pieces
> > of the LTO branch. The named address-spaces changes are still pending
> > review but I expect it to be merged befo
On Sat, Sep 19, 2009 at 10:57 PM, Richard Guenther wrote:
> Since the last status report we have merged the VTA branch and pieces
> of the LTO branch. The named address-spaces changes are still pending
> review but I expect it to be merged before the end of Stage 1.
> The rest of the LTO branch w
Status
==
The trunk is in Stage 1. Stage 1 will end on Sep 30th. After Stage 1
Stage 3 follows with only bugfixes and no new features allowed.
Stage 3 will end Nov 30th.
Since the last status report we have merged the VTA branch and pieces
of the LTO branch. The named address-spaces chan
22 matches
Mail list logo
