public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/21111] IA-64 NaT consumption faults due to uninitialized register reads
Date: Tue, 19 Jul 2005 06:26:00 -0000	[thread overview]
Message-ID: <20050719052409.20853.qmail@sourceware.org> (raw)
In-Reply-To: <20050419203158.21111.wilson@gcc.gnu.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-19 05:24 -------
(In reply to comment #3)
> Subject: Re:  IA-64 NaT consumption faults due to uninitialized
> The change I am suggesting should not hurt performance, and I expect 
> that it would actually help performance in many cases.
> 
> Currently, the first assignment to a structure is a bitfield insert.

This is PR 15596 and really an expand issue with respect with NVR.  Use the C++ front-end for both 
3.3 and 4.0.0 and noticed that it happens there too.

I would not doubt you could reproduce this with the C++ front-end before 4.0.0 also.  This is all NVR 
related and nothing more.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21111


  parent reply	other threads:[~2005-07-19  5:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 20:32 [Bug middle-end/21111] New: " wilson at gcc dot gnu dot org
2005-04-19 20:41 ` [Bug middle-end/21111] " wilson at gcc dot gnu dot org
2005-04-19 20:47 ` pinskia at gcc dot gnu dot org
2005-04-19 23:05 ` wilson at specifixinc dot com
2005-07-19  6:26 ` pinskia at gcc dot gnu dot org [this message]
     [not found] <bug-21111-4@http.gcc.gnu.org/bugzilla/>
2012-01-11 13:05 ` rguenth at gcc dot gnu.org
2021-10-11  7:53 ` rguenth at gcc dot gnu.org
2021-10-11  8:48 ` amonakov at gcc dot gnu.org
2021-10-11  9:18 ` rguenth at gcc dot gnu.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=20050719052409.20853.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).