public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ruschein@mail-infomine.ucr.edu (Johannes Ruscheinski)
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7373: g++ 3.0 and 3.1 miscompile certain uses of the ternary operator
Date: Mon, 22 Jul 2002 14:36:00 -0000	[thread overview]
Message-ID: <20020722213600.31407.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/7373; it has been noted by GNATS.

From: ruschein@mail-infomine.ucr.edu (Johannes Ruscheinski)
To: nathan@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, ruschein@infomine.ucr.edu, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/7373: g++ 3.0 and 3.1 miscompile certain uses of the ternary operator
Date: Mon, 22 Jul 2002 14:34:53 -0700

 Also sprach nathan@gcc.gnu.org:
 > Synopsis: g++ 3.0 and 3.1 miscompile certain uses of the ternary operator
 > 
 > State-Changed-From-To: open->closed
 > State-Changed-By: nathan
 > State-Changed-When: Mon Jul 22 14:12:46 2002
 > State-Changed-Why:
 >     not a bug. You need an out of class definition of those
 >     static members. (It is an opportunity for optimization,
 >     though)
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7373
 Thanks for your prompt reply.  The reason that I believed it to be a bug is that if
 you subtly change the code the linker error disappears.  Sorry to have wasted your
 time!
 -- 
 Johannes
 --
 Dr. Johannes Ruscheinski
 EMail:    ruschein_AT_infomine.ucr.edu ***          Linux                  ***
 Location: science library, room G40    *** The Choice Of A GNU Generation! ***
 Phone:    (909) 787-2279
 
 "To understand recursion, one must first understand recursion."
               -- Unknown
 


             reply	other threads:[~2002-07-22 21:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-22 14:36 Johannes Ruscheinski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-22 14:12 nathan
2002-07-22  9:06 ruschein

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=20020722213600.31407.qmail@sources.redhat.com \
    --to=ruschein@mail-infomine.ucr.edu \
    --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).