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 middle-end/60092] posix_memalign not recognized to derive alias and alignment info
Date: Wed, 12 Feb 2014 10:18:00 -0000 [thread overview]
Message-ID: <bug-60092-4-0WMhYo0cj6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60092-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60092
--- Comment #19 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Tobias Burnus from comment #18)
> (In reply to Richard Biener from comment #1)
> > We could "lower"
> > posix_memalign (&ptr, align, size);
> > to
> > posix_memalign (&ptr, align, size);
> > ptr = __builtin_assume_algined (ptr, align);
> > and hope for FRE to fix things up enough to make that useful.
>
>
> I wonder about mm_malloc. I assume for config/i386/pmm_malloc.h, it is
> already handled via posix_memalign, but shouldn't one also handle
> config/i386/gmm_malloc.h? For instance via
>
> --- a/gcc/config/i386/gmm_malloc.h
> +++ b/gcc/config/i386/gmm_malloc.h
> @@ -61,7 +61,11 @@ _mm_malloc (size_t size, size_t align)
> /* Store the original pointer just before p. */
> ((void **) aligned_ptr) [-1] = malloc_ptr;
>
> +#if defined(__GNUC__) && __GNUC__ >= 4 && __GNUC_MINOR__ >= 7
> + return __builtin_assume_aligned(aligned_ptr, align);
> +#else
> return aligned_ptr;
> +#endif
> }
>
> static __inline__ void
No, why? ccp of course understands the dynamic realignment:
aligned_ptr = (void *) (((size_t) malloc_ptr + align)
& ~((size_t) (align) - 1));
so will know that aligned_ptr is align bytes aligned.
next prev parent reply other threads:[~2014-02-12 10:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 10:22 [Bug middle-end/60092] New: " rguenth at gcc dot gnu.org
2014-02-06 10:22 ` [Bug middle-end/60092] " rguenth at gcc dot gnu.org
2014-02-06 10:32 ` jakub at gcc dot gnu.org
2014-02-06 11:34 ` rguenth at gcc dot gnu.org
2014-02-06 12:51 ` glisse at gcc dot gnu.org
2014-02-06 13:13 ` jakub at gcc dot gnu.org
2014-02-06 13:18 ` rguenth at gcc dot gnu.org
2014-02-06 13:42 ` jakub at gcc dot gnu.org
2014-02-06 14:07 ` rguenther at suse dot de
2014-02-06 14:08 ` jakub at gcc dot gnu.org
2014-02-06 14:45 ` rguenth at gcc dot gnu.org
2014-02-06 14:53 ` jakub at gcc dot gnu.org
2014-02-06 15:03 ` rguenther at suse dot de
2014-02-07 9:34 ` rguenth at gcc dot gnu.org
2014-02-07 13:41 ` rguenth at gcc dot gnu.org
2014-02-12 10:01 ` burnus at gcc dot gnu.org
2014-02-12 10:18 ` jakub at gcc dot gnu.org [this message]
2014-02-12 13:36 ` rguenth at gcc dot gnu.org
2014-02-14 16:11 ` ro at gcc dot gnu.org
2014-02-14 16:14 ` jakub at gcc dot gnu.org
2014-02-14 16:40 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-02-15 9:59 ` rguenth at gcc dot gnu.org
2014-02-18 14:52 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-04-22 11:36 ` jakub at gcc dot gnu.org
2014-04-28 14:36 ` rguenth at gcc dot gnu.org
2014-06-03 13:48 ` rguenth 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-60092-4-0WMhYo0cj6@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).