From: Jack Howarth <howarth@bromo.med.uc.edu>
To: Cary Coutant <ccoutant@google.com>
Cc: Richard Guenther <rguenther@suse.de>, gcc@gcc.gnu.org
Subject: Re: GCC 4.5 Status Report (2009-09-19)
Date: Mon, 21 Sep 2009 18:57:00 -0000 [thread overview]
Message-ID: <20090921185704.GA3598@bromo.med.uc.edu> (raw)
In-Reply-To: <c17be2b30909211123v27a16db1s5f042c98b2b1b25b@mail.gmail.com>
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 in the last
> >> couple of days? One of which will inevitably break trunk again and block all
> >> the others and then stage 1 will be over and it'll all be too late?
> >
> > I am not aware of any big patches that are still pending. Coming up
> > with new yet unknown things now wouldn't be a good timing anyway.
>
> I was hoping to get the dwarf4 branch merged into trunk during stage
> 1. While it's not a small patch, it's also not really that intrusive
> in that it consists mostly of new code that runs only with the
> -gdwarf-4 option. I've been testing it on a lot of big code bases for
> the last few months, and haven't found any new bugs for a more than a
> month now, so I think it's ready.
>
> I'll work on merging top-of-trunk into the branch early this week and
> then send a patch to merge back into the trunk.
>
> -cary
>
Cary,
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 -gstrict-dwarf
option which I guess should be expanded to cover your patch if
gcc 4.5 will be defaulting to -gdwarf-4 being enabled.
Jack
next prev parent reply other threads:[~2009-09-21 18:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 20:57 Richard Guenther
2009-09-19 22:03 ` Steven Bosscher
2009-09-19 22:22 ` Richard Guenther
2009-09-20 1:21 ` Geert Bosch
2009-09-20 1:00 ` Jack Howarth
2009-09-20 1:35 ` Dave Korn
2009-09-20 8:54 ` Richard Guenther
2009-09-20 11:38 ` Dave Korn
2009-09-20 11:48 ` Richard Guenther
2009-09-20 11:53 ` Dave Korn
2009-09-24 14:44 ` Jason Merrill
2009-09-24 14:50 ` Richard Guenther
2009-09-21 18:23 ` Cary Coutant
2009-09-21 18:57 ` Jack Howarth [this message]
2009-09-21 21:05 ` Cary Coutant
2009-09-21 21:10 ` Cary Coutant
2009-09-29 18:10 ` Sriraman Tallam
2009-09-29 22:08 ` Dave Korn
2009-09-29 22:59 ` Gerald Pfeifer
2009-09-30 10:40 ` Richard Guenther
2009-09-30 15:00 ` Jack Howarth
2009-10-01 0:17 ` Neil Vachharajani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090921185704.GA3598@bromo.med.uc.edu \
--to=howarth@bromo.med.uc.edu \
--cc=ccoutant@google.com \
--cc=gcc@gcc.gnu.org \
--cc=rguenther@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).