public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dberlin at dberlin dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/36830] [4.4 Regression] STORAGE_ERROR raised compiling s-os_lib.adb
Date: Sun, 27 Jul 2008 15:38:00 -0000 [thread overview]
Message-ID: <20080727153731.29455.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36830-276@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from dberlin at gcc dot gnu dot org 2008-07-27 15:37 -------
Subject: Re: [4.4 Regression] STORAGE_ERROR raised compiling s-os_lib.adb
No, it doesn't.
Even if the op isn't hashed, it is still compared for in
vn_reference_op_eq, so at worst the non-hashing will make it compare
more vn_reference_op's than it has to, it shouldn't affect
correctness.
On Sun, Jul 27, 2008 at 5:16 AM, ebotcazou at gcc dot gnu dot org
<gcc-bugzilla@gcc.gnu.org> wrote:
>
>
> ------- Comment #9 from ebotcazou at gcc dot gnu dot org 2008-07-27 09:16 -------
> This points to an immediate problem in vn_reference_op_compute_hash:
>
> /* Compute the hash for a reference operand VRO1. */
>
> static hashval_t
> vn_reference_op_compute_hash (const vn_reference_op_t vro1)
> {
> return iterative_hash_expr (vro1->op0, vro1->opcode)
> + iterative_hash_expr (vro1->op1, vro1->opcode);
> }
>
> op2 is not hashed (whereas it is on the 4.3 branch).
>
>
> --
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36830
>
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36830
next prev parent reply other threads:[~2008-07-27 15:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 1:53 [Bug tree-optimization/36830] New: " danglin at gcc dot gnu dot org
2008-07-15 12:07 ` [Bug tree-optimization/36830] " pinskia at gcc dot gnu dot org
2008-07-15 12:08 ` pinskia at gcc dot gnu dot org
2008-07-16 9:53 ` andreasmeier80 at gmx dot de
2008-07-18 17:05 ` rguenth at gcc dot gnu dot org
2008-07-20 21:27 ` danglin at gcc dot gnu dot org
2008-07-20 21:30 ` danglin at gcc dot gnu dot org
2008-07-21 12:55 ` andreasmeier80 at gmx dot de
2008-07-22 7:54 ` r dot emrich at de dot tecosim dot com
2008-07-23 9:36 ` ebotcazou at gcc dot gnu dot org
2008-07-27 9:04 ` ebotcazou at gcc dot gnu dot org
2008-07-27 9:16 ` ebotcazou at gcc dot gnu dot org
2008-07-27 15:38 ` dberlin at dberlin dot org [this message]
2008-07-27 15:59 ` ebotcazou at gcc dot gnu dot org
2008-07-27 16:57 ` ebotcazou at gcc dot gnu dot org
2008-07-27 16:59 ` ebotcazou at gcc dot gnu dot org
2008-07-27 17:04 ` ebotcazou at gcc dot gnu dot org
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=20080727153731.29455.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).