Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
		gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [rfc] add ppc testcase to test fpscr
Date: Tue, 02 Sep 2008 23:46:00 -0000	[thread overview]
Message-ID: <20080902234554.GC31087@caradoc.them.org> (raw)
In-Reply-To: <1220398310.4204.22.camel@localhost.localdomain>

On Tue, Sep 02, 2008 at 08:31:50PM -0300, Thiago Jung Bauermann wrote:
> > Looks OK to me, but I'm really wonderng why you added a '\r' at
> > the end of the expected output in our gdb_test calls.
> 
> That was the closest I could think of to an EOL marker. Using '$' is not
> an option, I believe.

You don't need an EOL marker; gdb_test adds \r\n after the supplied
pattern.

> > > +#include <stdio.h>
> > 
> > Is the use of stdio necessary in this case. If you can do without,
> > then this would allow us to run this testcase in the bareboard case
> > (powerpc-elf). Not strictly necessary, but nice to have...
> 
> I added the printf calls just to make sure GCC doesn't make the 'result'
> variable vanish. Maybe that's not necessary, since the asm blocks
> mention result as an output variable? Or maybe GCC would also nuke the
> asm blocks instead, seeing that they serve no useful purpose if 'result'
> is also not used? I don't know.

GCC won't eliminate user variables at -O0.  If you want the test to
work with optimization, or with non-GCC compilers, try making result a
volatile global.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-09-02 23:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21 23:18 Thiago Jung Bauermann
2008-08-21 23:32 ` Daniel Jacobowitz
2008-08-21 23:42   ` Thiago Jung Bauermann
2008-08-22  2:47     ` Daniel Jacobowitz
2008-08-22 18:13       ` Thiago Jung Bauermann
2008-09-02 21:40         ` Joel Brobecker
2008-09-02 23:35           ` Thiago Jung Bauermann
2008-09-02 23:46             ` Daniel Jacobowitz [this message]
2008-09-02 21:55         ` Daniel Jacobowitz
2008-09-03 20:15           ` Thiago Jung Bauermann
2008-09-03 21:01             ` Daniel Jacobowitz
2008-09-04  1:26               ` Thiago Jung Bauermann
2008-09-05  0:12                 ` Joel Brobecker
2008-09-05  3:38                   ` Thiago Jung Bauermann
2008-09-05 14:00                     ` Joel Brobecker
2008-09-05 19:30                       ` Thiago Jung Bauermann

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=20080902234554.GC31087@caradoc.them.org \
    --to=drow@false.org \
    --cc=bauerman@br.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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