http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37743
--- Comment #15 from Jakub Jelinek ---
Author: jakub
Date: Thu Mar 6 08:11:20 2014
New Revision: 208371
URL: http://gcc.gnu.org/viewcvs?rev=208371&root=gcc&view=rev
Log:
Backport from mainline
2014-02-19 Jakub Jelinek
PR c/37743
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37743
--- Comment #14 from Jakub Jelinek ---
Author: jakub
Date: Wed Feb 19 22:27:40 2014
New Revision: 207924
URL: http://gcc.gnu.org/viewcvs?rev=207924&root=gcc&view=rev
Log:
PR c/37743
* c-common.c (c_common_nodes_and_builtins): When initial
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37743
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37743
--- Comment #12 from Jakub Jelinek ---
Created attachment 32173
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32173&action=edit
gcc49-pr37743.patch
Untested fix. The deprecation can hopefully be done separately.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37743
--- Comment #11 from joseph at codesourcery dot com ---
Yes, we could do something like that (but I also think it's time to put
the targets without this type information on the deprecation list and warn
their maintainers that the target support
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37743
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #10
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37743
Hans-Peter Nilsson changed:
What|Removed |Added
Last reconfirmed|2009-03-31 20:40:20 |2013-12-1
CC|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37743
--- Comment #8 from Jeffrey Yasskin 2012-05-01
20:47:00 UTC ---
Arguably, the bad diagnostic (reporting "unsigned int!=unsigned int") is more
serious than the bswap bug, since it may show up for other functions.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37743
Jeffrey Yasskin changed:
What|Removed |Added
CC||jyasskin at gcc dot gnu.org
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37743
Richard Guenther changed:
What|Removed |Added
CC||hjl.tools at gmail dot com
--- Comment
--- Comment #5 from pinskia at gcc dot gnu dot org 2010-06-11 14:56 ---
*** Bug 44502 has been marked as a duplicate of this bug. ***
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
---
--- Comment #4 from jsm28 at gcc dot gnu dot org 2009-03-31 20:40 ---
Because my bug 448 patch isn't complete (doesn't give knowledge of the
stdint.h types for all targets), it doesn't yet fix this issue; it defines
c_uint32_type_node and c_uint64_type_node to be the normal C types used
--- Comment #3 from jakub at gcc dot gnu dot org 2008-10-07 13:22 ---
I think the warning is desirable, the code isn't portable to non-32bit int
targets. Wonder if we just shouldn't give a TYPE_NAME to uint32_type_node
and uint64_type_node (__builtin_uint32_t and __builtin_uint64_t or s
--- Comment #2 from pinskia at gcc dot gnu dot org 2008-10-06 21:56 ---
DEF_FUNCTION_TYPE_1 (BT_FN_UINT32_UINT32, BT_UINT32, BT_UINT32)
DEF_PRIMITIVE_TYPE (BT_UINT32, uint32_type_node)
Instead of using:
DEF_PRIMITIVE_TYPE (BT_UINT, unsigned_type_node)
But we need to use the 32bit type
--- Comment #1 from pinskia at gcc dot gnu dot org 2008-10-06 21:55 ---
DEF_GCC_BUILTIN(BUILT_IN_BSWAP32, "bswap32", BT_FN_UINT32_UINT32,
ATTR_CONST_NOTHROW_LIST)
This is caused by the fact __builtin_bswap32 uses uintSItype instead of the
normal unsignedint types.
--
http:/
15 matches
Mail list logo