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 lto/59326] FAIL: gcc.dg/vect/vect-simd-clone-*.c
Date: Thu, 28 Nov 2013 13:37:00 -0000	[thread overview]
Message-ID: <bug-59326-4-7pEpD8h2RJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59326-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59326

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #4)
> But then it won't handle the !node->definition cloning (it isn't actually
> cloning in that case, just creating another DECL_EXTERNAL FUNCTION_DECL with
> adjusted arguments).  So it really needs to be FOR_EACH_FUNCTION, but
> perhaps can avoid the cgraph_function_with_gimple_body_p/cgraph_get_body
> stuff if !node->definition.

Plus the DECL_ATTRIBUTES are there even without cgraph_get_body, right?
If yes, then the two new functions should go into expand_simd_clones after we
see whether we want to clone it at all, so perhaps best into simd_clone_create
's node->definition case right before cgraph_function_versioning.


  parent reply	other threads:[~2013-11-28 13:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28  9:16 [Bug c/59326] New: " dominiq at lps dot ens.fr
2013-11-28 11:08 ` [Bug lto/59326] " jakub at gcc dot gnu.org
2013-11-28 11:25 ` jakub at gcc dot gnu.org
2013-11-28 13:24 ` rguenth at gcc dot gnu.org
2013-11-28 13:26 ` rguenth at gcc dot gnu.org
2013-11-28 13:32 ` jakub at gcc dot gnu.org
2013-11-28 13:37 ` jakub at gcc dot gnu.org [this message]
2013-11-29 10:36 ` jakub at gcc dot gnu.org
2013-11-29 10:41 ` jakub at gcc dot gnu.org
2013-12-02 23:12 ` jakub 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-59326-4-7pEpD8h2RJ@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).