From: Jakub Jelinek <jakub@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, Bernd Schmidt <bernds@codesourcery.com>,
Cesar Philippidis <cesar@codesourcery.com>,
Chung-Lin Tang <cltang@codesourcery.com>,
James Norris <jnorris@codesourcery.com>,
Joseph Myers <joseph@codesourcery.com>,
Julian Brown <julian@codesourcery.com>,
Tom de Vries <tom@codesourcery.com>
Subject: Re: [gomp4] Assorted OpenACC changes (was: Next set of OpenACC changes)
Date: Thu, 14 May 2015 08:37:00 -0000 [thread overview]
Message-ID: <20150514081319.GJ1751@tucnak.redhat.com> (raw)
In-Reply-To: <87vbfwjj47.fsf@schwinge.name>
On Wed, May 13, 2015 at 10:52:08PM +0200, Thomas Schwinge wrote:
> In a similar vein, I have now committed the following to gomp-4_0-branch
> in r223178. This is not meant to be integrated into trunk as-is: there
> are incompatible libgomp ABI changes, for example. We'd still appreciate
ABI incompatible libgomp changes are absolute no-no. You need to provide
backwards compatibility...
Jakub
prev parent reply other threads:[~2015-05-14 8:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 8:54 Next set of OpenACC changes Thomas Schwinge
2015-05-05 8:56 ` Next set of OpenACC changes: middle end, libgomp Thomas Schwinge
2015-05-05 8:58 ` Next set of OpenACC changes: C family Thomas Schwinge
2015-05-05 14:19 ` Jakub Jelinek
2015-05-05 15:40 ` Cesar Philippidis
2015-05-05 8:59 ` Next set of OpenACC changes: Fortran Thomas Schwinge
2015-05-05 10:42 ` Bernhard Reutner-Fischer
2015-05-05 9:00 ` Next set of OpenACC changes: Testsuite Thomas Schwinge
2015-05-11 16:35 ` [gomp4] Next set of OpenACC changes Thomas Schwinge
2015-05-13 20:57 ` [gomp4] Assorted OpenACC changes (was: Next set of OpenACC changes) Thomas Schwinge
2015-05-14 8:37 ` Jakub Jelinek [this message]
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=20150514081319.GJ1751@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=bernds@codesourcery.com \
--cc=cesar@codesourcery.com \
--cc=cltang@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jnorris@codesourcery.com \
--cc=joseph@codesourcery.com \
--cc=julian@codesourcery.com \
--cc=thomas@codesourcery.com \
--cc=tom@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).