From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Pedro Alves'" <pedro@codesourcery.com>, <gdb-patches@sourceware.org>
Subject: [RFA-v2] testsuite: Avoid auto-import warning on cygwin/mingw
Date: Fri, 02 Oct 2009 07:29:00 -0000 [thread overview]
Message-ID: <009701ca4332$114bda50$33e38ef0$@u-strasbg.fr> (raw)
In-Reply-To: <200910020123.53952.pedro@codesourcery.com>
> > Is this OK?
> >
>
> I _think_ the idea is fine.
Thanks,
> IWBN to have basic tests covering
> printing auto-imported vs dllimported variables,
> and covering stepping into import-lib'ed dll functions (through
> the __imp_ trampolines).
Not sure, I really get this, sorry.
> > --- lib/gdb.exp 13 Jul 2009 19:24:18 -0000 1.119
> > +++ lib/gdb.exp 1 Oct 2009 22:03:25 -0000
> > @@ -1731,7 +1731,10 @@ proc gdb_compile {source dest type optio
> > lappend options "additional_flags=-L${outdir}"
> > } elseif { [istarget "mips-sgi-irix*"] } {
> > lappend options "additional_flags=-rpath
> ${outdir}"
> > - }
> > + } elseif { ([istarget "*-*-mingw*"]
> > + || [istarget *-*-cygwin*]) } {
> > + lappend new_options
> > "additional_flags=-Wl,--enable-auto-import"
>
> Did you mean 'lappend options'?
No, appending to options
would mean that this addition would be parsed by the loop
'foreach opt $options {'
of line 1713,
while adding it to new_options like it
is done also below for 'shlib_load'.
Furthermore, I always feel uncomfortable
when code inside a loop changes the variable
on which the loop is performed (options in that case.)
Wouldn't it be better to also
append to new_options for the two conditions above?
So, what about this?
2009-10-02 Pierre Muller <muller@ics.u-strasbg.fr>
* lib/gdb.exp (gdb_compile): Append added options
directly to new_options variable.
Add --enable-auto-import option for
mingw and cygwin targets.
Index: lib/gdb.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/lib/gdb.exp,v
retrieving revision 1.119
diff -u -p -r1.119 gdb.exp
--- lib/gdb.exp 13 Jul 2009 19:24:18 -0000 1.119
+++ lib/gdb.exp 2 Oct 2009 07:26:54 -0000
@@ -1728,10 +1728,13 @@ proc gdb_compile {source dest type optio
if { ([test_compiler_info "gcc-*"]
&& ([istarget "powerpc*-*-aix*"]
|| [istarget "rs6000*-*-aix*"] )) } {
- lappend options "additional_flags=-L${outdir}"
+ lappend new_options "additional_flags=-L${outdir}"
} elseif { [istarget "mips-sgi-irix*"] } {
- lappend options "additional_flags=-rpath ${outdir}"
- }
+ lappend new_options "additional_flags=-rpath ${outdir}"
+ } elseif { ([istarget "*-*-mingw*"]
+ || [istarget *-*-cygwin*]) } {
+ lappend new_options
"additional_flags=-Wl,--enable-auto-import"
+ }
}
} elseif { $opt == "shlib_load" } {
if { ([istarget "*-*-mingw*"]
next prev parent reply other threads:[~2009-10-02 7:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 22:09 [RFA] " Pierre Muller
2009-10-02 0:24 ` Pedro Alves
2009-10-02 7:29 ` Pierre Muller [this message]
2009-10-02 18:09 ` [RFA-v2] " Pedro Alves
2009-10-02 20:57 ` Tom Tromey
2009-10-02 21:35 ` Pierre Muller
2009-10-02 22:19 ` Pedro Alves
2009-10-02 22:27 ` Pierre Muller
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='009701ca4332$114bda50$33e38ef0$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
/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