From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Alexander Yermolovich <ayermolo@fb.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"maskray@google.com" <maskray@google.com>,
Mark Wielaard <mark@klomp.org>,
David Blaikie <dblaikie@gmail.com>
Subject: Re: DWARF64 gcc/clang flag discussion
Date: Mon, 7 Dec 2020 12:22:41 +0100 [thread overview]
Message-ID: <20201207112241.GQ3788@tucnak> (raw)
In-Reply-To: <CAFiYyc386WWm6E7EEHMZ1dPmnUZ=n9FWLWi=Kp2ErVigfvvyew@mail.gmail.com>
On Mon, Dec 07, 2020 at 08:14:20AM +0100, Richard Biener via Gcc wrote:
> > Sorry, just going around in circles a bit, I guess this may be a better
> > summary:
> > If I had to pick a -g flag/semantic for this, I guess I'd pick
> > -gdwarf32/64 without implied -g. I'd pick that if I knew GCC would
> > implement it to match - but if GCC might go either way on implied -g, I
> > think I'd rather avoid changing the semantics of the flag later on & use a
> > different name GCC isn't likely to define different semantics for (and I'd
> > probably pick -fdwarf32/64).
> >
> >
> > There's an approved patch to add -gdwarf{32,64} not implying -g
> > [Alex] Do you happen to have a link on hand to it?
> >
>
> https://gcc.gnu.org/pipermail/gcc-patches/2020-December/560734.html
Note, the change is already in GCC trunk.
Jakub
next prev parent reply other threads:[~2020-12-07 11:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 20:22 Alexander Yermolovich
2020-11-21 0:19 ` mark
2020-11-23 8:32 ` Richard Biener
2020-11-24 2:38 ` David Blaikie
2020-11-24 2:59 ` Jeff Law
2020-11-24 3:03 ` David Blaikie
2020-11-24 3:21 ` Jeff Law
2020-11-24 7:45 ` Jakub Jelinek
2020-11-24 7:50 ` Richard Biener
2020-11-24 11:04 ` Mark Wielaard
2020-11-24 11:11 ` Jakub Jelinek
2020-11-24 15:22 ` Jeff Law
2020-11-24 18:38 ` David Blaikie
2020-11-25 9:22 ` Richard Biener
2020-11-25 21:46 ` David Blaikie
2020-11-30 19:35 ` Alexander Yermolovich
2020-11-30 20:08 ` Fāng-ruì Sòng
2020-11-30 20:09 ` David Blaikie
2020-12-01 1:04 ` Alexander Yermolovich
2020-12-01 18:33 ` David Blaikie
2020-12-02 18:43 ` Alexander Yermolovich
2020-12-02 21:12 ` David Blaikie
2020-12-03 1:10 ` Alexander Yermolovich
2020-12-03 17:52 ` David Blaikie
2020-12-04 8:36 ` Richard Biener
2020-12-04 18:01 ` Alexander Yermolovich
2020-12-07 7:14 ` Richard Biener
2020-12-07 11:22 ` Jakub Jelinek [this message]
2020-12-07 19:08 ` David Blaikie
2020-11-30 20:25 ` Mark Wielaard
2020-11-24 18:32 ` David Blaikie
2020-11-24 18:59 ` Eric Botcazou
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=20201207112241.GQ3788@tucnak \
--to=jakub@redhat.com \
--cc=ayermolo@fb.com \
--cc=dblaikie@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@klomp.org \
--cc=maskray@google.com \
--cc=richard.guenther@gmail.com \
/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).