From: Joe Buck <jbuck@synopsys.COM>
To: florian@edamail.fishkill.ibm.com (Florian Krohm)
Cc: guillaume.thouvenin@polymtl.ca (Guillaume),
jbuck@synopsys.COM (Joe Buck),
gcc@gcc.gnu.org
Subject: Re: fdump-ast-original and strg:
Date: Fri, 23 Nov 2001 10:56:00 -0000 [thread overview]
Message-ID: <200111301822.KAA28472@atrus.synopsys.com> (raw)
In-Reply-To: <01113013120701.01459@warp9.fishkill.ibm.com> from "Florian Krohm" at Nov 30, 2001 01:12:07 PM
[ fixing the dump format to be able to read back strings ]
The correct solution, in my opinion, is to produce a valid C string
literal. This can always be done, for any input, and furthermore
there should already be routines in the compiler that you can use
(though I can't be more specific off the top of my head). Don't try
to invent a new format.
WARNING: multiple messages have this Message-ID
From: Joe Buck <jbuck@synopsys.COM>
To: florian@edamail.fishkill.ibm.com (Florian Krohm)
Cc: guillaume.thouvenin@polymtl.ca (Guillaume),
jbuck@synopsys.COM (Joe Buck),
gcc@gcc.gnu.org
Subject: Re: fdump-ast-original and strg:
Date: Fri, 30 Nov 2001 10:22:00 -0000 [thread overview]
Message-ID: <200111301822.KAA28472@atrus.synopsys.com> (raw)
Message-ID: <20011130102200.a69esFHgewZU9E-uIZDqVbTHRx1-BPCag1Tmg-el_-E@z> (raw)
In-Reply-To: <01113013120701.01459@warp9.fishkill.ibm.com>
[ fixing the dump format to be able to read back strings ]
The correct solution, in my opinion, is to produce a valid C string
literal. This can always be done, for any input, and furthermore
there should already be routines in the compiler that you can use
(though I can't be more specific off the top of my head). Don't try
to invent a new format.
next prev parent reply other threads:[~2001-11-30 18:22 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 13:14 Guillaume
2001-11-22 13:14 ` Joe Buck
2001-11-23 8:49 ` Guillaume
2001-11-23 8:52 ` Florian Krohm
2001-11-23 10:56 ` Joe Buck [this message]
2001-11-30 10:22 ` Joe Buck
2001-11-23 11:04 ` Dale Johannesen
2001-11-23 16:20 ` TImode ?inhibited? in main 3.1 branch davide.rossetti
2001-11-30 12:31 ` davide.rossetti
2001-11-23 17:46 ` fdump-ast-original and strg: Tim Hollebeek
2001-11-23 18:26 ` Dale Johannesen
2001-11-30 15:02 ` Dale Johannesen
2001-11-30 14:59 ` Tim Hollebeek
2001-11-30 10:24 ` Dale Johannesen
2001-11-23 11:14 ` Zack Weinberg
2001-11-23 14:13 ` Florian Krohm
2001-11-23 14:42 ` Joe Buck
2001-11-23 23:16 ` Richard Henderson
2001-11-24 3:30 ` Zack Weinberg
2001-11-24 3:38 ` Richard Henderson
2001-11-30 15:50 ` Richard Henderson
2001-11-30 15:37 ` Zack Weinberg
2001-11-30 15:28 ` Richard Henderson
2001-11-30 11:01 ` Joe Buck
2001-11-30 10:54 ` Florian Krohm
2001-11-23 16:40 ` Guillaume
2001-11-30 13:55 ` Guillaume
2001-11-30 10:26 ` Zack Weinberg
2001-11-30 10:12 ` Florian Krohm
2001-11-30 9:54 ` Guillaume
2001-11-29 19:00 ` Joe Buck
2001-11-29 18:46 ` Guillaume
2001-11-24 11:14 mike stump
2001-11-24 12:41 ` Joe Buck
2001-11-30 17:12 ` Joe Buck
2001-11-30 16:59 ` mike stump
2001-11-24 14:37 mike stump
2001-11-24 17:15 ` Joseph S. Myers
2001-11-30 18:35 ` Joseph S. Myers
2001-12-03 14:23 ` Richard Henderson
2001-11-30 17:49 ` mike stump
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=200111301822.KAA28472@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=florian@edamail.fishkill.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=guillaume.thouvenin@polymtl.ca \
/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).