Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, toolchain-devel@blackfin.uclinux.org
Subject: Re: [PATCH] sim: tests: support .S files
Date: Mon, 14 Mar 2011 21:06:00 -0000	[thread overview]
Message-ID: <201103141649.50396.vapier@gentoo.org> (raw)
In-Reply-To: <201103141156.23648.pedro@codesourcery.com>

[-- Attachment #1: Type: Text/Plain, Size: 1244 bytes --]

On Monday, March 14, 2011 07:56:23 Pedro Alves wrote:
> On Sunday 13 March 2011 23:10:48, Mike Frysinger wrote:
> > -       set comp_output [target_assemble $sourcefile ${name}.o
> > "$as_options $global_as_options"]
> > +       if [string match "*.S" $sourcefile] {
> > +           set comp_output [target_compile $sourcefile ${name}.s
> > "preprocess" "incdir=$srcdir/$subdir"]
> > +           if ![string match "" $comp_output] {
> > +               verbose -log "$comp_output" 3
> > +               fail "$mach $testname (preprocessing)"
> > +               continue
> > +           }
> > +           set comp_output [target_assemble ${name}.s ${name}.o
> > "$as_options $global_as_options"]
> > +           file delete ${name}.s
> > +       } else {
> > +           set comp_output [target_assemble $sourcefile ${name}.o
> > "$as_options $global_as_options"]
> > +       }
> 
> When using srcdir==buildir, won't this overwrite the source file on
> non case-sensitive filesystems?

picking any diff named file runs the risk of collision.  i have a local patch 
to follow this up to add support for .c files too, but i guess i'll just fold 
them into one since the .c step goes .c -> .o without the .s step.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-03-14 20:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14  8:20 Mike Frysinger
2011-03-14 12:32 ` Pedro Alves
2011-03-14 21:06   ` Mike Frysinger [this message]
2011-03-14 21:23 ` [PATCH] sim: tests: support .S/.c files Mike Frysinger
2011-03-23 10:40   ` Mike Frysinger
2011-03-23 17:02   ` Joel Brobecker
2011-03-23 18:50     ` Mike Frysinger
2011-03-24  5:38     ` Mike Frysinger
2011-03-29  3:06   ` Mike Frysinger
2011-05-14 17:48   ` Mike Frysinger
2011-05-16 18:37     ` Joel Brobecker
2011-05-16 18:49       ` Mike Frysinger
  -- strict thread matches above, loose matches on Subject: below --
2010-03-14 22:02 [PATCH] sim: tests: support .S files Mike Frysinger
2010-03-15  0:43 ` Matt Rice
2010-03-15  1:46   ` Jie Zhang
2010-03-15  7:09   ` Mike Frysinger
2010-03-15 10:54     ` Matt Rice
2010-03-19 20:12       ` Mike Frysinger
2010-03-15 20:17   ` DJ Delorie

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=201103141649.50396.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=toolchain-devel@blackfin.uclinux.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