public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/65419] incorrect sibcalls to libgomp functions
Date: Wed, 27 May 2015 22:06:00 -0000	[thread overview]
Message-ID: <bug-65419-4-JqtuFsAFG7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65419-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65419

--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to vries from comment #10)
> Created attachment 35639 [details]
> tentative patch for GOACC_data_end

That is a bad idea, as void GOACC_data_end (void) is already exported out of
libgomp, so this is an ABI break.

If it is meant as a hack around not specifying the functions to aliasing oracle
properly, and not really needed after expansion to RTL, you could e.g. use an
internal function in GIMPLE and then lower it to normal function call that
doesn't take the argument.


  parent reply	other threads:[~2015-05-27 22:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 17:52 [Bug fortran/65419] New: " cesar at gcc dot gnu.org
2015-03-18 13:45 ` [Bug fortran/65419] " cesar at gcc dot gnu.org
2015-05-27  9:37 ` [Bug tree-optimization/65419] " vries at gcc dot gnu.org
2015-05-27 11:43 ` vries at gcc dot gnu.org
2015-05-27 16:02 ` vries at gcc dot gnu.org
2015-05-27 16:13 ` cesar at gcc dot gnu.org
2015-05-27 16:55 ` vries at gcc dot gnu.org
2015-05-27 17:12 ` jakub at gcc dot gnu.org
2015-05-27 19:05 ` vries at gcc dot gnu.org
2015-05-27 22:00 ` vries at gcc dot gnu.org
2015-05-27 22:06 ` jakub at gcc dot gnu.org [this message]
2015-05-28  9:27 ` vries at gcc dot gnu.org
2015-05-28  9:44 ` vries at gcc dot gnu.org
2015-05-28 14:18 ` vries at gcc dot gnu.org
2015-06-02  8:52 ` vries at gcc dot gnu.org

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=bug-65419-4-JqtuFsAFG7@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).