public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/9675: store-and-increment becomes  increment-and-store
Date: Thu, 13 Feb 2003 09:46:00 -0000	[thread overview]
Message-ID: <20030213094602.17830.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/9675; it has been noted by GNATS.

From: Richard Earnshaw <rearnsha@arm.com>
To: "RenE J.V. Bertin" <rjvbertin@hotmail.com>
Cc: rearnsha@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
        josh@joshisanerd.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: optimization/9675: store-and-increment becomes 
 increment-and-store
Date: Thu, 13 Feb 2003 09:40:48 +0000

 > On 12 Feb 2003 18:54:38 -0000, rearnsha@gcc.gnu.org wrote regarding "Re: optimization/9675:
 > store-and-increment becomes increment-and-store"
 > 
 > I'm informing myself a bit more about the undefined issue (the expr. uses the pointed-to value but increments the pointer). HOWEVER, it may interest you to know that if you modify downcase() to 
 > 
 > void downcase( char *s )
 > { char c;
 >    while( *s ){
 > 		c= *s;
 > 		*s++= tolower( c );
 > 	}
 > }
 > 
 > the coredump issue remains (using compilation as shown in coredumps.log). According to your reply, the above does not contain undefined statements, and -Wsequence-point doesn't complain about any.
 > 
 
 The code above is ok.  Are you trying to downcase a string literal?
 
 R.
 


             reply	other threads:[~2003-02-13  9:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13  9:46 Richard Earnshaw [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-12 18:54 rearnsha
2003-02-12 18:46 rjvbertin

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=20030213094602.17830.qmail@sources.redhat.com \
    --to=rearnsha@arm.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).