From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix free_lang_data on asm stmts (PR lto/91572)
Date: Sun, 01 Sep 2019 11:55:00 -0000 [thread overview]
Message-ID: <20190901115514.GI2120@tucnak> (raw)
In-Reply-To: <6DE9EA1F-FDC4-4ADB-B3FB-213E2AD0D184@suse.de>
On Sat, Aug 31, 2019 at 03:02:18PM +0200, Richard Biener wrote:
> Ok, but I wonder if we can stream the constraint strings in a simpler way - surely the type doesn't really matter?
> Why are they not identifier nodes?
I guess they have type because they are parsed like any other string
literals during parsing and once we parse them that way, it isn't worth
changing them to something else like an identifier.
Would it be enough to just clear their type during free lang data or
something similar?
Jakub
next prev parent reply other threads:[~2019-09-01 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-31 12:04 Jakub Jelinek
2019-08-31 15:42 ` Richard Biener
2019-09-01 11:55 ` Jakub Jelinek [this message]
2019-09-01 12:30 ` Richard Biener
2019-09-01 16:28 ` Jakub Jelinek
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=20190901115514.GI2120@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).