public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/37897] New: decNumber functions break strict-aliasing rules Date: Wed, 22 Oct 2008 22:38:00 -0000 [thread overview] Message-ID: <bug-37897-4503@http.gcc.gnu.org/bugzilla/> (raw) The decNumber package in GCC provides support for decimal floating point arithmetic in the compiler and, for the DPD format, in libgcc's runtime support for decimal float. Some of the code in decNumber violates C's strict-aliasing rules and has resulted in warnings for quite some time. Some of that code has different results since the addition of patch r136695, leading to the failure of test gcc.dg/dfp/convert-int-max.c. The code in question has undefined behavior so I can't say that it is miscompiled, only that the results are different. I'm testing a patch that quiets all of the warnings about dereferencing type-punned pointers with very few changes to the decNumber code, mostly changes to data types and access macros. This PR is to keep track of the change because the decNumber code from GCC is also used by the GDB project and a branch in EGLIBC. -- Summary: decNumber functions break strict-aliasing rules Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: janis at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37897
next reply other threads:[~2008-10-22 22:38 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-22 22:38 janis at gcc dot gnu dot org [this message] 2008-10-22 22:39 ` [Bug other/37897] " janis at gcc dot gnu dot org 2008-10-23 10:12 ` rguenth at gcc dot gnu dot org 2008-10-23 16:17 ` janis at gcc dot gnu dot org 2008-10-27 16:48 ` janis at gcc dot gnu dot org 2008-10-27 18:19 ` janis at gcc dot gnu dot org 2008-10-31 19:51 ` janis at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-37897-4503@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).