public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>, Joel Brobecker <brobecker@gnat.com>
Subject: Re: [PATCH][gdb/testsuite] Handle unrecognized command line option in gdb_compile_test
Date: Fri, 10 Sep 2021 18:38:26 +0200	[thread overview]
Message-ID: <d61d81d5-d0d4-637a-5ae6-0e8850703038@suse.de> (raw)
In-Reply-To: <20210908112058.GA15665@delia>

On 9/8/21 1:20 PM, Tom de Vries wrote:
> Hi,
> 
> When running the gdb testsuite with gnatmake-4.8, I get many fails of the
> following form:
> ...
> gcc: error: unrecognized command line option '-fgnat-encodings=all'^M
> gnatmake: "gdb.ada/O2_float_param/foo.adb" compilation error^M
> compiler exited with status 1
> compilation failed: gcc ... gdb.ada/O2_float_param/foo.adb
> gcc: error: unrecognized command line option '-fgnat-encodings=all'
> gnatmake: "gdb.ada/O2_float_param/foo.adb" compilation error
> FAIL: gdb.ada/O2_float_param.exp: scenario=all: compilation foo.adb
> ...
> 
> Fix this by marking the test unsupported instead, such that we have:
> ...
> UNSUPPORTED: gdb.ada/O2_float_param.exp: scenario=all: compilation foo.adb \
>   (unsupported option '-fgnat-encodings=all')
> ...

I've committed this non-controversial part and backported to gdb-11-branch.

Thanks,
- Tom

      parent reply	other threads:[~2021-09-10 16:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08 11:20 Tom de Vries
2021-09-08 12:22 ` Joel Brobecker
2021-09-08 13:45   ` Tom de Vries
2021-09-08 14:12     ` Joel Brobecker
2021-09-10 16:38 ` Tom de Vries [this message]

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=d61d81d5-d0d4-637a-5ae6-0e8850703038@suse.de \
    --to=tdevries@suse.de \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).