public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/66015] New: align directives not propagated after __attribute__ ((__optimize__ ("O2")))
@ 2015-05-05 10:39 chrbr at gcc dot gnu.org
  2015-05-06 10:55 ` [Bug target/66015] " chrbr at gcc dot gnu.org
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: chrbr at gcc dot gnu.org @ 2015-05-05 10:39 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 66015
           Summary: align directives not propagated after __attribute__
                    ((__optimize__ ("O2")))
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: chrbr at gcc dot gnu.org
  Target Milestone: ---

When attribute optimize is used, the alignment flags are not reevaluated.

Consequently, the functions are not aligned as if they were with the same
global flag

for example:
__attribute__ ((__optimize__ ("O2")))
void
hooray ()
{
}

is not aligned 

The second consequence is that can_inline_edge_p fails because opts_for_fn
(caller->decl) != opts_for_fn (callee->decl)) even-though they are compiled
with the same optimization level.


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2015-05-18  7:26 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-05-05 10:39 [Bug target/66015] New: align directives not propagated after __attribute__ ((__optimize__ ("O2"))) chrbr at gcc dot gnu.org
2015-05-06 10:55 ` [Bug target/66015] " chrbr at gcc dot gnu.org
2015-05-06 11:20 ` chrbr at gcc dot gnu.org
2015-05-07  7:35 ` uros at gcc dot gnu.org
2015-05-07 19:36 ` uros at gcc dot gnu.org
2015-05-15 14:34 ` ramana at gcc dot gnu.org
2015-05-18  7:26 ` chrbr at gcc dot gnu.org

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).