public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c/8379: bits/byteswap.h mistakenly redefines __bswap_16 instead of __bswap_32 when using constant definition
@ 2003-01-08  2:46 bangerth
  0 siblings, 0 replies; 3+ messages in thread
From: bangerth @ 2003-01-08  2:46 UTC (permalink / raw)
  To: fabio.torchetti, gcc-bugs, gcc-prs, nobody

Synopsis: bits/byteswap.h mistakenly redefines __bswap_16 instead of __bswap_32 when using constant definition

State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Tue Jan  7 18:46:23 2003
State-Changed-Why:
    I think the file you are refering to is
    /usr/include/bits/byteswap.h, right? In that case, it is
    out of reach of gcc, and you should file a report with
    the linux kernel or glibc people, whoever is responsible
    for that file.
    
    For what it's worth, this erroneous definition is not in
    my SuSE 8.0 installation (yes, I always knew that these
    German products are much better :-))
    
    Cheers
      Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8379


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

* Re: c/8379: bits/byteswap.h mistakenly redefines __bswap_16 instead of __bswap_32 when using constant definition
@ 2003-01-08 13:17 reichelt
  0 siblings, 0 replies; 3+ messages in thread
From: reichelt @ 2003-01-08 13:17 UTC (permalink / raw)
  To: fabio.torchetti, gcc-bugs, gcc-prs, nobody

Synopsis: bits/byteswap.h mistakenly redefines __bswap_16 instead of __bswap_32 when using constant definition

State-Changed-From-To: feedback->closed
State-Changed-By: reichelt
State-Changed-When: Wed Jan  8 05:17:34 2003
State-Changed-Why:
    This is actually a glibc bug which has been fixed, see
    http://bugs.gnu.org/cgi-bin/gnatsweb.pl?debug=&database=glibc&cmd=view+audit-trail&pr=4760

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8379


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

* c/8379: bits/byteswap.h mistakenly redefines __bswap_16 instead of __bswap_32 when using constant definition
@ 2002-10-28  5:56 fabio.torchetti
  0 siblings, 0 replies; 3+ messages in thread
From: fabio.torchetti @ 2002-10-28  5:56 UTC (permalink / raw)
  To: gcc-gnats


>Number:         8379
>Category:       c
>Synopsis:       bits/byteswap.h mistakenly redefines __bswap_16 instead of __bswap_32 when using constant definition
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          mistaken
>Submitter-Id:   net
>Arrival-Date:   Mon Oct 28 05:56:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Fabio Torchetti
>Release:        gcc (GCC) 3.2
>Organization:
>Environment:
Linux/RH8.0 default installation
>Description:
In bits/byteswap.h we have the following fallback in case the compiler is not running on __GNUCC_ > 2 (...or this is not defined.):

Line 83:
#else
# define __bswap_16(x) \
     (__extension__                                                           \
      ({ register unsigned int __x = (x); __bswap_constant_32 (__x); }))
#endif

This should actually be:

#else
# define __bswap_32(x) \
     (__extension__                                                           \
      ({ register unsigned int __x = (x); __bswap_constant_32 (__x); }))
#endif

...or so I guess.
>How-To-Repeat:
Just compile anything without defining __GNUCC__ > 2
>Fix:
As shown above

>Release-Note:
>Audit-Trail:
>Unformatted:


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

end of thread, other threads:[~2003-01-08 13:17 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-01-08  2:46 c/8379: bits/byteswap.h mistakenly redefines __bswap_16 instead of __bswap_32 when using constant definition bangerth
  -- strict thread matches above, loose matches on Subject: below --
2003-01-08 13:17 reichelt
2002-10-28  5:56 fabio.torchetti

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