From: Eric Botcazou <ebotcazou@adacore.com>
To: gcc-patches@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>
Cc: Richard Biener <richard.guenther@gmail.com>
Subject: Re: [patch] Fix GC issue triggered by arithmetic overflow checking
Date: Thu, 13 Oct 2016 10:59:00 -0000 [thread overview]
Message-ID: <1545012.AjIN00x9ch@polaris> (raw)
In-Reply-To: <20161013103735.GD7282@tucnak.redhat.com>
> I guess it depends on whether temp$8 and temp$low overlap or not.
I don't think so, the code is identical so that would be a more serious bug:
struct cpp_num
{
cpp_num_part high;
cpp_num_part low;
bool unsignedp;
bool overflow;
};
I think it's just dwarf2out_var_location being sensitive to the ordering.
--
Eric Botcazou
prev parent reply other threads:[~2016-10-13 10:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-08 18:56 Eric Botcazou
2016-10-10 8:59 ` Richard Biener
2016-10-10 10:38 ` Eric Botcazou
2016-10-10 10:45 ` Richard Biener
2016-10-11 8:05 ` Eric Botcazou
2016-10-16 18:57 ` Eric Botcazou
2016-10-17 8:40 ` Richard Biener
2016-10-10 10:49 ` Richard Biener
2016-10-13 10:16 ` Eric Botcazou
2016-10-13 10:20 ` Richard Biener
2016-10-13 10:37 ` Jakub Jelinek
2016-10-13 10:59 ` Eric Botcazou [this message]
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=1545012.AjIN00x9ch@polaris \
--to=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).