From: Jakub Jelinek <jakub@redhat.com>
To: Nathan Sidwell <nathan@acm.org>
Cc: Tom de Vries <tdevries@suse.de>,
Cesar Philippidis <cesar@codesourcery.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH,nvptx] Truncate config/nvptx/oacc-parallel.c
Date: Wed, 01 Aug 2018 17:34:00 -0000 [thread overview]
Message-ID: <20180801173434.GS17988@tucnak> (raw)
In-Reply-To: <77b7afc6-2e79-fc43-6263-3327d0407c92@acm.org>
On Wed, Aug 01, 2018 at 10:13:06AM -0700, Nathan Sidwell wrote:
> On 08/01/2018 04:55 AM, Jakub Jelinek wrote:
>
> > The ABI compatibility is mainly for libgomp.so which hasn't (ever) bumped
> > the soname and I don't plan to do that any time soon, but even for the
> > offloaded libgomp.a I guess one might compile with GCC 5 and link with GCC
> > 9 and expect things not to fail miserably. This is a *.a library, can't you
>
> I think it should fail horribly. If it succeeded, the performance would
> suck. Far better to shout at the user sooner.
Ok, I can live with that for OpenACC and GCC 5, just would not like to force
people to rebuild everything every time GCC is bumped even for OpenACC (and
once exported symbols from libgomp.so need to stay forever, unless soname is
bumnped).
Jakub
next prev parent reply other threads:[~2018-08-01 17:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 21:58 Remove unused openacc call Nathan Sidwell
2016-04-20 8:47 ` Thomas Schwinge
2016-04-20 10:27 ` Jakub Jelinek
2018-07-31 15:55 ` [PATCH,nvptx] Truncate config/nvptx/oacc-parallel.c Cesar Philippidis
2018-08-01 11:32 ` Tom de Vries
2018-08-01 11:55 ` Jakub Jelinek
2018-08-01 12:31 ` Tom de Vries
2018-08-01 17:13 ` Nathan Sidwell
2018-08-01 17:34 ` Jakub Jelinek [this message]
2019-05-06 8:52 ` [committed] Clean up libgomp GCC 5 legacy support (was: Remove unused openacc call) 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=20180801173434.GS17988@tucnak \
--to=jakub@redhat.com \
--cc=cesar@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathan@acm.org \
--cc=tdevries@suse.de \
/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).