public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug testsuite/108152] New: gcc.dg/pr71558.c fails for LLP64
@ 2022-12-17  7:26 nightstrike at gmail dot com
  2022-12-17  7:30 ` [Bug testsuite/108152] " pinskia at gcc dot gnu.org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: nightstrike at gmail dot com @ 2022-12-17  7:26 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 108152
           Summary: gcc.dg/pr71558.c fails for LLP64
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
          Assignee: unassigned at gcc dot gnu.org
          Reporter: nightstrike at gmail dot com
  Target Milestone: ---

gcc.dg/pr71558.c has the following lines:

__SIZE_TYPE__ strlen (const char *);
void *malloc (__SIZE_TYPE__);
__SIZE_TYPE__ b = strlen (a);


These are good in that they support LLP64 through size_t, however they fail
because this test case is compiled with -ansi.  When using -ansi, the following
warnings appear:

gcc.dg/pr71558.c:6:1: error: ISO C90 does not support 'long long' [-Wlong-long]
gcc.dg/pr71558.c:7:1: error: ISO C90 does not support 'long long' [-Wlong-long]
gcc.dg/pr71558.c:14:1: error: ISO C90 does not support 'long long'
[-Wlong-long]


And of course, on LLP64 systems, __SIZE_TYPE__ is in fact a long long. 
Hopefully, -ansi can just be removed from the compile options, although I don't
know how to do that.

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

* [Bug testsuite/108152] gcc.dg/pr71558.c fails for LLP64
  2022-12-17  7:26 [Bug testsuite/108152] New: gcc.dg/pr71558.c fails for LLP64 nightstrike at gmail dot com
@ 2022-12-17  7:30 ` pinskia at gcc dot gnu.org
  2022-12-21  3:49 ` nightstrike at gmail dot com
  2022-12-30  1:26 ` nightstrike at gmail dot com
  2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2022-12-17  7:30 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
{ dg-options "" }

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

* [Bug testsuite/108152] gcc.dg/pr71558.c fails for LLP64
  2022-12-17  7:26 [Bug testsuite/108152] New: gcc.dg/pr71558.c fails for LLP64 nightstrike at gmail dot com
  2022-12-17  7:30 ` [Bug testsuite/108152] " pinskia at gcc dot gnu.org
@ 2022-12-21  3:49 ` nightstrike at gmail dot com
  2022-12-30  1:26 ` nightstrike at gmail dot com
  2 siblings, 0 replies; 4+ messages in thread
From: nightstrike at gmail dot com @ 2022-12-21  3:49 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #2 from nightstrike <nightstrike at gmail dot com> ---
(In reply to Andrew Pinski from comment #1)
> { dg-options "" }

That would remove every option, no?  Do others matter, like -pedantic, or
whatever else is there?

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

* [Bug testsuite/108152] gcc.dg/pr71558.c fails for LLP64
  2022-12-17  7:26 [Bug testsuite/108152] New: gcc.dg/pr71558.c fails for LLP64 nightstrike at gmail dot com
  2022-12-17  7:30 ` [Bug testsuite/108152] " pinskia at gcc dot gnu.org
  2022-12-21  3:49 ` nightstrike at gmail dot com
@ 2022-12-30  1:26 ` nightstrike at gmail dot com
  2 siblings, 0 replies; 4+ messages in thread
From: nightstrike at gmail dot com @ 2022-12-30  1:26 UTC (permalink / raw)
  To: gcc-bugs

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

nightstrike <nightstrike at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |10walls at gmail dot com

--- Comment #3 from nightstrike <nightstrike at gmail dot com> ---
(In reply to Andrew Pinski from comment #1)
> { dg-options "" }

So just to be pedantic (pun intended!), the options currently in use are:

-fdiagnostics-plain-output -ansi -pedantic-errors


If we use dg-options "", both -ansi and -pedantic-errors are removed. 
-fdiagnostics-plain-output stays.  Is this ok?

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

end of thread, other threads:[~2022-12-30  1:26 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-17  7:26 [Bug testsuite/108152] New: gcc.dg/pr71558.c fails for LLP64 nightstrike at gmail dot com
2022-12-17  7:30 ` [Bug testsuite/108152] " pinskia at gcc dot gnu.org
2022-12-21  3:49 ` nightstrike at gmail dot com
2022-12-30  1:26 ` nightstrike at gmail dot com

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