public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jerry DeLisle <jvdelisle@charter.net>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>,
	fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] fortran/openmp.c -- Fix bootstrap
Date: Sun, 22 Nov 2015 19:18:00 -0000	[thread overview]
Message-ID: <5652150C.5070705@charter.net> (raw)
In-Reply-To: <20151122185949.GA53877@troutmask.apl.washington.edu>

On 11/22/2015 10:59 AM, Steve Kargl wrote:
> I have no idea if this is actually correct, but it restores bootstrap.
> OK to commit?
> 

This looks correct to me. There should be no more in the lists than
OMP_LIST_NUM. Was there a PR for this and do we know when it broke?

Jerry



  reply	other threads:[~2015-11-22 19:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02 13:46 OpenACC declare directive updates James Norris
     [not found] ` <5639FAC0.2090104@codesourcery.com>
     [not found]   ` <20151106193127.GI5675@tucnak.redhat.com>
     [not found]     ` <563D0345.7010208@codesourcery.com>
     [not found]       ` <20151106194909.GK5675@tucnak.redhat.com>
     [not found]         ` <878u5n7pqk.fsf@hertz.schwinge.homeip.net>
     [not found]           ` <56451FE6.3040200@codesourcery.com>
2015-11-22 18:59             ` [PATCH] fortran/openmp.c -- Fix bootstrap Steve Kargl
2015-11-22 19:18               ` Jerry DeLisle [this message]
2015-11-22 19:27               ` James Norris
     [not found]               ` <564DF738.80706@codesourcery.com>
2015-11-27 11:37                 ` [gomp4] Re: OpenACC declare directive updates Thomas Schwinge
2019-06-18 23:02                   ` [committed] [PR85221] Set 'omp declare target', 'omp declare target link' attributes for Fortran OpenACC 'declare'd variables (was: [gomp4] Re: OpenACC declare directive updates) Thomas Schwinge

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=5652150C.5070705@charter.net \
    --to=jvdelisle@charter.net \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=sgk@troutmask.apl.washington.edu \
    /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).