From: David Blaikie <dblaikie@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: "mark@klomp.org" <mark@klomp.org>,
Alexander Yermolovich <ayermolo@fb.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"ikudrin@accesssoftek.com" <ikudrin@accesssoftek.com>,
"maskray@google.com" <maskray@google.com>
Subject: Re: DWARF64 gcc/clang flag discussion
Date: Mon, 23 Nov 2020 18:38:16 -0800 [thread overview]
Message-ID: <CAENS6EvLs8i7siGrqCgzcx1y8Q6fA0Yh2HwpH5h9Ca3sdPca5g@mail.gmail.com> (raw)
In-Reply-To: <CAFiYyc0QcyETRaF5y2p2gNhDWbQ+vW9+Ud98HZz1ZwXVm-v2yQ@mail.gmail.com>
On Mon, Nov 23, 2020 at 12:32 AM Richard Biener
<richard.guenther@gmail.com> wrote:
>
> On Sat, Nov 21, 2020 at 1:21 AM mark@klomp.org <mark@klomp.org> wrote:
> >
> > On Fri, Nov 20, 2020 at 08:22:26PM +0000, Alexander Yermolovich wrote:
> > > On llvm side of compiler world there has been work done by Igor Kudrin to enable DWARF64.
> > > I am trying to add a flag to Clang to enable DWARF64 generation. https://reviews.llvm.org/D90507
> > > In review David Blaikie pointed out that there has been a discussion on what to call this flag:
> > > https://linuxplumbersconf.org/event/7/contributions/746/attachments/578/1018/DWARF5-64.pdf
> > > https://linuxplumbersconf.org/event/7/sessions/90/attachments/583/1201/dwarf-bof-notes-aug24-lpc-2020.txt
> > > https://www.mail-archive.com/gcc@gcc.gnu.org/msg92495.html
> > >
> > > Reading through that it doesn't look like there is a consensus on what it should be.
> > >
> > > From discussion there is seems to be mixed opinion if it should be
> > > -f<name> or -g<name>. Primarily centered around if -g prefix implies
> > > turning on generation of debug information.
> > >
> > > Now that LLVM can actually generate DWARF64 for ELF, can we come to consensus on the name?
> >
> > I don't believe any firm consensus was reached on naming yet. But I
> > would pick -fdwarf32/-fdwarf64.
>
> I would pick -gdwarf32/-gdwarf64 (are we sure the DWARF spec will
> never reach version 32 or 64?
> maybe -g32 / -g64 similar to -m32/-m64 are good enough?)
Any sense of a good way to break the tie/uncertainty?
Alternatively: If Clang picks something here (likely from within this
range of candidates - though given I've got a fair bit of say on the
Clang side, and if left to me, I'd probably lean heavily on the
-fdwarf32/64 side), is it likely that choice will tend to be adopted
by GCC? I'd rather not get out of sync, but I expect a bit hard to get
a conclusion on the GCC side without patches in progress, etc. Got a
sense of who are the people who would likely be deciders/patch
approvers for such a naming choice on the GCC side?
- Dave
next prev parent reply other threads:[~2020-11-24 2:38 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 [this message]
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
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=CAENS6EvLs8i7siGrqCgzcx1y8Q6fA0Yh2HwpH5h9Ca3sdPca5g@mail.gmail.com \
--to=dblaikie@gmail.com \
--cc=ayermolo@fb.com \
--cc=gcc@gcc.gnu.org \
--cc=ikudrin@accesssoftek.com \
--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).