[Bug testsuite/108150] gcc.dg/attr-aligned.c fails with incorrect max alignment

[cvs-commit at gcc dot gnu.org via Gcc-bugs]

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

--- Comment #4 from CVS Commits  ---
The master branch has been updated by Jonathan Yong :

https://gcc.gnu.org/g:ff3d99c5e72126cf8d4c7611a63a82dfc476cdbe

commit r13-5474-gff3d99c5e72126cf8d4c7611a63a82dfc476cdbe
Author: Jonathan Yong <10wa...@gmail.com>
Date:   Sun Jan 8 01:28:34 2023 +

PR c/108150 - Fix alignment test for Windows targets

gcc/testsuite/ChangeLog:

PR c/108150
* gcc.dg/attr-aligned.c: Make errors emitted on Windows
target same as on Linux.

Signed-off-by: Jonathan Yong <10wa...@gmail.com>

[Bug testsuite/108150] gcc.dg/attr-aligned.c fails with incorrect max alignment

[10walls at gmail dot com via Gcc-bugs]

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

--- Comment #3 from jon_y <10walls at gmail dot com> ---
Created attachment 54211
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54211&action=edit
Fix attempt 1

Makes errors emitted same as on Linux.

[Bug testsuite/108150] gcc.dg/attr-aligned.c fails with incorrect max alignment

[nightstrike at gmail dot com via Gcc-bugs]

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

nightstrike  changed:

   What|Removed |Added

 CC||10walls at gmail dot com

--- Comment #2 from nightstrike  ---
It occurs to me, if GCC already internally knows the max alignment (since it's
outputting it in the warning message), why do we need to have such complicated
preprocessor magic to guess at what the alignment is?  Would it be easier to
have GCC just define __GCC_MAX_ALIGNMENT__ or something similar for all
targets, and then use that in the test?

[Bug testsuite/108150] gcc.dg/attr-aligned.c fails with incorrect max alignment

[nightstrike at gmail dot com via Gcc-bugs]

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

--- Comment #1 from nightstrike  ---
Ok, that was dumb.. WINT_MAX is wide int max... hah.  So maybe test for
__CYGWIN__ || __WIN32__