RFC: PATCH to consider MAX_OFILE_ALIGNMENT for targetm.absolute_biggest_alignment
Bernd Schmidt
bschmidt@redhat.com
Tue Sep 13 11:03:00 GMT 2016
On 09/12/2016 08:58 PM, Jason Merrill wrote:
> TARGET_ABSOLUTE_BIGGEST_ALIGNMENT is documented to be the largest
> alignment possible for any type or variable, and defaults to
> BIGGEST_ALIGNMENT. But MAX_OFILE_ALIGNMENT is typically much larger
> than BIGGEST_ALIGNMENT, and is documented as the limit for __attribute
> ((aligned)). Shouldn't it be considered in the default for
> absolute_biggest_alignment? But if we make that change, I expect that
> your ACCEL_COMPILER streamer-in change would become a no-op. What was
> that change intended to accomplish? I'm not finding anything about it
> in gcc-patches.
https://gcc.gnu.org/ml/gcc-patches/2014-11/msg00003.html
Its only purpose is to limit alignments when offloading to a different
target. You may be right about having to use MAX_OFILE_ALIGNMENT; I
suppose defining it to 64 on nvptx would still work.
Bernd
More information about the Gcc-patches
mailing list