From: "Giovanni Bajo" <rasky@develer.com>
To: "Ebke, Hans-Christian" <h.ebke@kostal.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: extension to -fdump-tree-*-raw
Date: Fri, 22 Jul 2005 10:50:00 -0000 [thread overview]
Message-ID: <028401c58eaa$f9506ff0$bf03030a@trilan> (raw)
In-Reply-To: <D3E67AD42B61D7119DD600306E2132C109516FE4@debemail01>
Ebke, Hans-Christian <h.ebke@kostal.com> wrote:
> I have to write this in Outlook, so I don't even try to get the quoting
> right. Sorry. :-(
http://jump.to/outlook-quotefix
> But it would break applications relying on the old format.
There is no format either. dump-tree is *very* specific of GCC inners, and
it can dramatically changes between releases. OK, maybe not the syntax, but
the semantic. I wouldn't care of the syntax at that point.
--
Giovanni Bajo
next prev parent reply other threads:[~2005-07-22 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 10:40 AW: " Ebke, Hans-Christian
2005-07-22 10:50 ` Giovanni Bajo [this message]
2005-07-22 11:08 ` Gabriel Dos Reis
-- strict thread matches above, loose matches on Subject: below --
2005-07-25 5:47 Ebke, Hans-Christian
2005-07-22 10:06 Ebke, Hans-Christian
2005-07-22 10:27 ` Giovanni Bajo
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='028401c58eaa$f9506ff0$bf03030a@trilan' \
--to=rasky@develer.com \
--cc=gcc@gcc.gnu.org \
--cc=h.ebke@kostal.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).