public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "johnnybit at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/101261] New: clones for target_clones attribute cannot be created when compilling with -fno-semantic-interposition Date: Tue, 29 Jun 2021 17:02:50 +0000 [thread overview] Message-ID: <bug-101261-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101261 Bug ID: 101261 Summary: clones for target_clones attribute cannot be created when compilling with -fno-semantic-interposition Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: johnnybit at gmail dot com Target Milestone: --- darktable's user reported problem building darktable with "optimized" flags and I could confirm the error is present on GCC 10.3.0 When compilling whole darktable with CFLAGS set to `-march=native -O3 -fno-semantic-interposition -flto=3 -fno-plt -fgraphite-identity -floop-nest-optimize -fuse-linker-plugin -pipe -Wl,-O1 -Wl,--as-needed` the compiler errors with: src/common/iop_profile.c:1015:6: error: clones for «target_clones» attribute cannot be created 1015 | void dt_ioppr_transform_image_colorspace(struct dt_iop_module_t *self, const float *const image_in, | ^ I've managed to narrow it down and it was enough to just set the -fno-semantic-interposition flag to make darktable compillation error out on the same point. I haven't been able to create minimum reproducer for this problem (single file project compiles and runs ok) for details please check https://github.com/darktable-org/darktable/issues/9303
next reply other threads:[~2021-06-29 17:02 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-29 17:02 johnnybit at gmail dot com [this message] 2021-06-29 17:13 ` [Bug middle-end/101261] " pinskia at gcc dot gnu.org 2021-06-30 4:38 ` marxin at gcc dot gnu.org 2021-08-13 8:24 ` marxin at gcc dot gnu.org 2021-08-13 8:36 ` marxin at gcc dot gnu.org 2021-08-13 9:01 ` marxin at gcc dot gnu.org 2021-08-13 13:44 ` [Bug ipa/101261] " cvs-commit at gcc dot gnu.org 2021-08-13 13:45 ` marxin at gcc dot gnu.org 2021-08-16 11:14 ` cvs-commit at gcc dot gnu.org 2021-08-16 11:16 ` marxin 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-101261-4@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: linkBe 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).