public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/51883] New: Build warning unknown conversion type in gimplify.c
@ 2012-01-17 15:42 mdblack98 at yahoo dot com
2012-01-17 16:24 ` [Bug c/51883] " manu at gcc dot gnu.org
2012-01-17 18:39 ` mdblack98 at yahoo dot com
0 siblings, 2 replies; 3+ messages in thread
From: mdblack98 at yahoo dot com @ 2012-01-17 15:42 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51883
Bug #: 51883
Summary: Build warning unknown conversion type in gimplify.c
Classification: Unclassified
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: mdblack98@yahoo.com
../../gcc-4.6.2/gcc/gimplify.c: In function
\u2018omp_notice_threadprivate_variable\u2019:
../../gcc-4.6.2/gcc/gimplify.c:5575: warning: unknown conversion type character
\u2018E\u2019 in format
../../gcc-4.6.2/gcc/gimplify.c:5575: warning: too many arguments for format
../../gcc-4.6.2/gcc/gimplify.c: In function \u2018omp_notice_variable\u2019:
../../gcc-4.6.2/gcc/gimplify.c:5636: warning: unknown conversion type character
\u2018E\u2019 in format
../../gcc-4.6.2/gcc/gimplify.c:5636: warning: too many arguments for format
../../gcc-4.6.2/gcc/gimplify.c: In function \u2018omp_is_private\u2019:
../../gcc-4.6.2/gcc/gimplify.c:5746: warning: unknown conversion type character
\u2018E\u2019 in format
../../gcc-4.6.2/gcc/gimplify.c:5746: warning: too many arguments for format
../../gcc-4.6.2/gcc/gimplify.c:5760: warning: unknown conversion type character
\u2018E\u2019 in format
../../gcc-4.6.2/gcc/gimplify.c:5760: warning: too many arguments for format
../../gcc-4.6.2/gcc/gimplify.c:5763: warning: unknown conversion type character
\u2018E\u2019 in format
../../gcc-4.6.2/gcc/gimplify.c:5763: warning: too many arguments for format
../../gcc-4.6.2/gcc/gimplify.c: In function
\u2018gimplify_scan_omp_clauses\u2019:
../../gcc-4.6.2/gcc/gimplify.c:5926: warning: unknown conversion type character
\u2018E\u2019 in format
../../gcc-4.6.2/gcc/gimplify.c:5926: warning: too many arguments for format
^ permalink raw reply [flat|nested] 3+ messages in thread* [Bug c/51883] Build warning unknown conversion type in gimplify.c
2012-01-17 15:42 [Bug c/51883] New: Build warning unknown conversion type in gimplify.c mdblack98 at yahoo dot com
@ 2012-01-17 16:24 ` manu at gcc dot gnu.org
2012-01-17 18:39 ` mdblack98 at yahoo dot com
1 sibling, 0 replies; 3+ messages in thread
From: manu at gcc dot gnu.org @ 2012-01-17 16:24 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51883
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |manu at gcc dot gnu.org
Resolution| |INVALID
--- Comment #1 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-01-17 16:12:55 UTC ---
GCC is built in stages. The first stage uses the system compiler, which may
have bugs or not handle special conversion type characters handled by the GCC
version being built (this particular warning). Therefore, warnings produced by
the system compiler are often wrong. Please, do not report them.
http://gcc.gnu.org/wiki/FAQ#stage1warnings
It would be nice to NOT produce any warning during stage 1, but I guess people
are happy enough just ignoring them to not bother sending a patch to fix the
build scripts. The build system of GCC is a huge complex mess, so one needs a
very good reason to play games with it.
^ permalink raw reply [flat|nested] 3+ messages in thread* [Bug c/51883] Build warning unknown conversion type in gimplify.c
2012-01-17 15:42 [Bug c/51883] New: Build warning unknown conversion type in gimplify.c mdblack98 at yahoo dot com
2012-01-17 16:24 ` [Bug c/51883] " manu at gcc dot gnu.org
@ 2012-01-17 18:39 ` mdblack98 at yahoo dot com
1 sibling, 0 replies; 3+ messages in thread
From: mdblack98 at yahoo dot com @ 2012-01-17 18:39 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51883
--- Comment #2 from mdblack98 at yahoo dot com 2012-01-17 17:13:20 UTC ---
I should have realized that. Indeed those warning don't show up in later
stages.
Sorry for the noise.
-----Original Message-----
From: manu at gcc dot gnu.org [mailto:gcc-bugzilla@gcc.gnu.org]
Sent: Tuesday, January 17, 2012 10:13 AM
To: mdblack98@yahoo.com
Subject: [Bug c/51883] Build warning unknown conversion type in gimplify.c
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51883
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |manu at gcc dot gnu.org
Resolution| |INVALID
--- Comment #1 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-01-17
16:12:55 UTC ---
GCC is built in stages. The first stage uses the system compiler, which may
have bugs or not handle special conversion type characters handled by the GCC
version being built (this particular warning). Therefore, warnings produced by
the system compiler are often wrong. Please, do not report them.
http://gcc.gnu.org/wiki/FAQ#stage1warnings
It would be nice to NOT produce any warning during stage 1, but I guess people
are happy enough just ignoring them to not bother sending a patch to fix the
build scripts. The build system of GCC is a huge complex mess, so one needs a
very good reason to play games with it.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-01-17 17:13 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-01-17 15:42 [Bug c/51883] New: Build warning unknown conversion type in gimplify.c mdblack98 at yahoo dot com
2012-01-17 16:24 ` [Bug c/51883] " manu at gcc dot gnu.org
2012-01-17 18:39 ` mdblack98 at yahoo 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).