public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aweiner at lsil dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/14896] Fails to generate code for structure field assignment when assigning first field and assignment is within an infinite loop
Date: Mon, 12 Apr 2004 15:40:00 -0000	[thread overview]
Message-ID: <20040412151705.21398.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040408225018.14896.aweiner@lsil.com>


------- Additional Comments From aweiner at lsil dot com  2004-04-12 15:17 -------
Subject: RE:  Fails to generate code for structure field assi
	gnment when assigning first field and assignment is within an infinite lo
	op

That's plausible, but why does the compiler not exhibit consistent behavior
across all fields of the structure? It only seems exhibits this behavior for
the first element of the structure; it compiles assignments for all
subsequent elements.

-----Original Message-----
From: pinskia at gcc dot gnu dot org [mailto:gcc-bugzilla@gcc.gnu.org]
Sent: Thursday, April 08, 2004 4:07 PM
To: aweiner@lsil.com
Subject: [Bug c/14896] Fails to generate code for structure field
assignment when assigning first field and assignment is within an
infinite loop



------- Additional Comments From pinskia at gcc dot gnu dot org  2004-04-08
23:06 -------
This is invalid, you should use volatile keyword to keep the store in there.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


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

------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.


-- 


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


      parent reply	other threads:[~2004-04-12 15:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 22:50 [Bug c/14896] New: " aweiner at lsil dot com
2004-04-08 23:06 ` [Bug c/14896] " pinskia at gcc dot gnu dot org
2004-04-12 15:40 ` aweiner at lsil dot com [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=20040412151705.21398.qmail@sources.redhat.com \
    --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).