From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>,
gcc-patches@gcc.gnu.org, Mark Wielaard <mjw@redhat.com>
Subject: Re: [patch+7.9] compile: Filter out -fpreprocessed
Date: Tue, 03 Feb 2015 18:59:00 -0000 [thread overview]
Message-ID: <20150203185912.GA26920@host1.jankratochvil.net> (raw)
In-Reply-To: <CADPb22SBOPJAS4vDNX_SESXupv6NiYiPxbxa1WmQogDVtqchQQ@mail.gmail.com>
On Tue, 03 Feb 2015 19:50:40 +0100, Doug Evans wrote:
> On Fri, Jan 16, 2015 at 2:42 PM, Jan Kratochvil
> <jan.kratochvil@redhat.com> wrote:
> > [...]
> > It is wrong that gcc puts -fpreprocessed into DW_AT_producer - I may post a gcc
> > patch for it.
>
> Hi.
> I wasn't aware there are now rules for what can and cannot go in DW_AT_producer.
> DW_AT_producer has gone from being informational to having a formal
> spec (in the sense that something will break if, for example, a
> particular option is mentioned).
> Is this spec written down somewhere? [At least guidelines for what
> things may lead to breakage?]
No. Do you have a suggestion where to put it? Should it be only a GNU
extension or should it be even DWARF-standardized?
Jan
next prev parent reply other threads:[~2015-02-03 18:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 22:42 Jan Kratochvil
2015-01-17 10:02 ` [patchv2+7.9] " Jan Kratochvil
2015-02-03 7:56 ` Joel Brobecker
2015-02-03 17:25 ` [commit+7.9] " Jan Kratochvil
2015-02-03 18:50 ` [patch+7.9] " Doug Evans
2015-02-03 18:59 ` Jan Kratochvil [this message]
2015-02-03 19:10 ` Mark Wielaard
2015-02-04 18:15 ` Doug Evans
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=20150203185912.GA26920@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mjw@redhat.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