public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sandra Loosemore <sandra@codesourcery.com>
To: Tobias Burnus <tobias@codesourcery.com>,
	Jakub Jelinek <jakub@redhat.com>
Cc: Richard Biener <rguenther@suse.de>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	 Thomas Schwinge <thomas@codesourcery.com>
Subject: Re: [Patch] Add 'default' to -foffload=; document that flag [PR67300]
Date: Mon, 28 Jun 2021 16:34:58 -0600	[thread overview]
Message-ID: <974de942-bd3d-430b-3edd-3db294175659@codesourcery.com> (raw)
In-Reply-To: <4af01e92-c1e7-8cfc-d635-45aba3a48232@codesourcery.com>

On 6/28/21 9:51 AM, Tobias Burnus wrote:
> I managed to delete the libgomp part before posting the patch, hence, 
> reposted.
> 
> (The change from -foffload= to -foffload-options= ensures that also 
> other configured compilers such as GCN are used, an issue that Thomas 
> found. The original -foffload=nvptx-none=-latomic was added because as 
> otherwise the GCN part caused build issues for Richard.)
> 
> Thus, this patch is like v3, except for the invoke.texi fixes suggested 
> by Sandra (thanks!) + adding a ChangeLog
> and like v4, except the lost libgomp changes has been re-added (+ 
> ChangeLog update).
> 
> I hope it now is fine.

Hmmm.

> --- a/gcc/doc/invoke.texi
> +++ b/gcc/doc/invoke.texi
> @@ -197,17 +197,17 @@ in the following sections.
>  
>  @item C Language Options
>  @xref{C Dialect Options,,Options Controlling C Dialect}.
> -@gccoptlist{-ansi  -std=@var{standard}  -fgnu89-inline @gol
> --fpermitted-flt-eval-methods=@var{standard} @gol
> --aux-info @var{filename}  -fallow-parameterless-variadic-functions @gol
> --fno-asm  -fno-builtin  -fno-builtin-@var{function}  -fgimple@gol
> --fhosted  -ffreestanding @gol
> +@gccoptlist{-ansi  -std=@var{standard}  -aux-info @var{filename} @gol
> +-fallow-parameterless-variadic-functions  -fno-asm  @gol
> +-fno-builtin  -fno-builtin-@var{function}  -fcond-mismatch @gol
> +-ffreestanding  -fgimple  -fgnu-tm  -fgnu89-inline  -fhosted @gol
> +-flax-vector-conversions  -fms-extensions @gol
>  -fopenacc  -fopenacc-dim=@var{geom} @gol
> +-foffload=@var{arg} -foffload-options=@var{arg} @gol

Still need two spaces between these options on the same line inside 
@gccoptlist.

>  -fopenmp  -fopenmp-simd @gol
> --fms-extensions  -fplan9-extensions  -fsso-struct=@var{endianness} @gol
> --fallow-single-precision  -fcond-mismatch  -flax-vector-conversions @gol
> --fsigned-bitfields  -fsigned-char @gol
> --funsigned-bitfields  -funsigned-char}
> +-fpermitted-flt-eval-methods=@var{standard} @gol
> +-fplan9-extensions -fsigned-bitfields -funsigned-bitfields @gol
> +-fsigned-char -funsigned-char -fsso-struct=@var{endianness}}

And on both the last two lines here.

I didn't think it was necessary to alphabetize the actual documentation 
of the options (only the table in the option summary).  I'll have to 
assume that you didn't actually change any of the text you moved around. 
  The text for -foffload and -foffload-options looks fine now.

The documentation part of the patch is OK with the whitespace changes 
(no need to post another version for me to review that).

-Sandra

  reply	other threads:[~2021-06-28 22:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17 12:08 Tobias Burnus
2021-06-17 12:27 ` Jakub Jelinek
2021-06-17 16:03   ` Tobias Burnus
2021-06-17 17:41     ` Sandra Loosemore
2021-06-17 17:50       ` Jakub Jelinek
2021-06-17 19:28         ` Tobias Burnus
2021-06-17 19:40           ` Jakub Jelinek
2021-06-17 21:57             ` Sandra Loosemore
2021-06-17 23:05               ` Tobias Burnus
2021-06-18 22:47                 ` Sandra Loosemore
2021-06-28 11:28                   ` Tobias Burnus
2021-06-28 15:51                     ` Tobias Burnus
2021-06-28 22:34                       ` Sandra Loosemore [this message]
2021-06-29 11:58                       ` Jakub Jelinek
2021-06-29 13:47                         ` Tobias Burnus
2021-06-29 13:51                           ` Jakub Jelinek
2021-06-29 20:47                           ` Rainer Orth
2021-06-29 21:02                             ` Christophe Lyon
2021-06-30 20:12                             ` Rainer Orth

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=974de942-bd3d-430b-3edd-3db294175659@codesourcery.com \
    --to=sandra@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=rguenther@suse.de \
    --cc=thomas@codesourcery.com \
    --cc=tobias@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).