public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-227] doc/install.texi: Document --enable-offload-defaulted config option
Date: Wed, 28 Apr 2021 19:38:30 +0000 (GMT)	[thread overview]
Message-ID: <20210428193830.44B17394480C@sourceware.org> (raw)

https://gcc.gnu.org/g:4c84c45d8ab5ef55aabef18da17244dc13170f9c

commit r12-227-g4c84c45d8ab5ef55aabef18da17244dc13170f9c
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Wed Apr 28 21:15:16 2021 +0200

    doc/install.texi: Document --enable-offload-defaulted config option
    
    Document configure --enable-offload-defaulted option added in
    commit r12-218-gfe5bfa6704179f8db7d1ae0b485439e9896df8eb
    
    gcc/ChangeLog:
    
            * doc/install.texi (--enable-offload-defaulted): Document.

Diff:
---
 gcc/doc/install.texi | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 4c38244ae58..d2cab15d9fd 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -2239,6 +2239,14 @@ specifying paths @var{path1}, @dots{}, @var{pathN}.
     --enable-offload-targets=x86_64-intelmicemul-linux-gnu=/path/to/x86_64/compiler,nvptx-none
 @end smallexample
 
+@item --enable-offload-defaulted
+
+Tell GCC that configured but not installed offload compilers and libgomp
+plugins are silently ignored.  Useful for distribution compilers where
+those are in separate optional packages and where the presence or absence
+of those optional packages should determine the actual supported offloading
+target set rather than the GCC configure-time selection.
+
 @item --with-hsa-runtime=@var{pathname}
 @itemx --with-hsa-runtime-include=@var{pathname}
 @itemx --with-hsa-runtime-lib=@var{pathname}


                 reply	other threads:[~2021-04-28 19:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210428193830.44B17394480C@sourceware.org \
    --to=burnus@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).