Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Christian Biesinger <cbiesinger@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] Add gdb_compile_openmp to lib/gdb.exp
Date: Thu, 22 Aug 2019 17:27:00 -0000	[thread overview]
Message-ID: <20190822102716.45bdd1a8@f29-4.lan> (raw)
In-Reply-To: <CAPTJ0XEGDDzVVk7z21a_15gh25JMztkR7VQ_AZyKBd6c_BB-dw@mail.gmail.com>

On Thu, 22 Aug 2019 12:18:13 -0500
Christian Biesinger <cbiesinger@google.com> wrote:

> > +# Build an OpenMP program from SOURCE.  See prefatory comment for
> > +# gdb_compile, above, for discussion of the parameters to this proc.
> > +
> > +proc gdb_compile_openmp {source dest type options} {
> > +    switch -glob [test_compiler_info] {
> > +        "gcc-*" {
> > +            if { !([istarget "*-*-cygwin*"]
> > +                   || [istarget "*-*-mingw*"]
> > +                   || [istarget "*-*-pe*"]) } {
> > +                lappend options "additional_flags=-fopenmp"  
> 
> Why exclude cygwin/mingw here?

No good reason.  I've removed those lines from my local sources.

Thanks for noticing this.

Kevin


  reply	other threads:[~2019-08-22 17:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-22 17:14 [PATCH 0/2] OpenMP parallel region scope tests Kevin Buettner
2019-08-22 17:14 ` [PATCH 1/2] Add gdb_compile_openmp to lib/gdb.exp Kevin Buettner
2019-08-22 17:18   ` Christian Biesinger via gdb-patches
2019-08-22 17:27     ` Kevin Buettner [this message]
2019-08-22 17:14 ` [PATCH 2/2] OpenMP parallel region scope tests Kevin Buettner
2019-09-30 16:22   ` Tom Tromey
2019-11-04  4:31     ` Kevin Buettner
2019-10-02 16:52   ` Pedro Alves
2019-11-04  4:49     ` Kevin Buettner
2019-09-07 15:51 ` [PING][PATCH 0/2] " Kevin Buettner
2019-09-28 20:10 ` [PING 2][PATCH " Kevin Buettner

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=20190822102716.45bdd1a8@f29-4.lan \
    --to=kevinb@redhat.com \
    --cc=cbiesinger@google.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