public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/9700: va_start gets __offset wrong in some situations
Date: Sat, 15 Feb 2003 02:36:00 -0000	[thread overview]
Message-ID: <20030215023600.9061.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Aron Griffis <agriffis@gentoo.org>
Cc: bangerth@dealii.org, <bjb@gentoo.org>, <gcc-bugs@gcc.gnu.org>,
   <msterret@coat.com>, <wwoods@gentoo.org>, <gcc-gnats@gcc.gnu.org>
Subject: Re: c/9700: va_start gets __offset wrong in some situations
Date: Fri, 14 Feb 2003 20:29:14 -0600 (CST)

 On Fri, 14 Feb 2003, Aron Griffis wrote:
 
 > bangerth@dealii.org wrote:[Fri Feb 14 2003, 09:10:12PM EST]
 > >     Admittedly I only looked at the program given in the first
 > >     report. So, let me ask again: I think that that program
 > >     does exactly what should be expected, is this right? If so,
 > >     the comment in that program about expectations is wrong.
 > 
 > Ah, this is where we're not communicating.  The comment is accurate.  I
 > can rephrase it as follows, perhaps this is more clear:
 > 
 >     /*
 >      * This is the first invocation of va_arg.  The argument list is as
 >      * follows:
 >      *
 >      * 		a = 0
 >      * 		b = 0
 >      * 		c = 0
 >      * 		d = 0
 >      * 		e = 0
 >      * 		ap = { undef, undef }
 >      * 		first_custom = "one"
 >      * 		... = "two", "three"
 >      *
 >      * Therefore va_arg should return "two".  However in this example it
 >      * erroneously returns "one", which is first_custom.
 >      */
 
 OK. It seems as if I misread it. 
 
 In any case, the program does as expected on my x86 linux machine. I can't
 compile the second program on my machine, as you mention. So I assume that
 this is something that is specific to the alpha port. I'll change the 
 synopsis accordingly, and leave this to the port maintainers.
 
 Thanks for keeping me on track ;-)
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-02-15  2:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-15  2:36 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-15  2:26 Aron Griffis
2003-02-15  2:10 bangerth
2003-02-15  1:56 Aron Griffis
2003-02-15  0:14 bangerth
2003-02-14  5:26 agriffis

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=20030215023600.9061.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.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).