OpenE2K/gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Trying again to fix aligned-new on m68k.

Browse Source 
* c-common.c (check_cxx_fundamental_alignment_constraints): Don't
	limit types at all.

From-SVN: r240110
This commit is contained in:
Jason Merrill 2016-09-13 09:15:39 -04:00 committed by Jason Merrill
parent 4c13ba175a
commit 9453eee910
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gcc/c-family/ChangeLog
View File

@ -1,3 +1,8 @@
2016-09-13 Jason Merrill <jason@redhat.com>
* c-common.c (check_cxx_fundamental_alignment_constraints): Don't
limit types at all.
2016-09-12 Jason Merrill <jason@redhat.com> 2016-09-12 Jason Merrill <jason@redhat.com>
* c-common.c (check_cxx_fundamental_alignment_constraints): Fix * c-common.c (check_cxx_fundamental_alignment_constraints): Fix

9
gcc/c-family/c-common.c
View File

@ -7905,13 +7905,8 @@ check_cxx_fundamental_alignment_constraints (tree node,
} }
else if (TYPE_P (node)) else if (TYPE_P (node))
{ {
/* Let's be liberal for types. BIGGEST_ALIGNMENT is the largest /* Let's be liberal for types; don't limit their alignment any more than
alignment a built-in type can require, MAX_OFILE_ALIGNMENT is the check_user_alignment already did. */
largest alignment the object file can represent, but a type that is
only allocated dynamically could request even larger alignment. So
only limit type alignment to what TYPE_ALIGN can represent. */
if (requested_alignment > (max_align = 8U << 28))
alignment_too_large_p = true;
} }
if (alignment_too_large_p) if (alignment_too_large_p)