public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: eckart@icd.de To: gcc-gnats@gcc.gnu.org Subject: c/7895: Bit-field initialization incorrect after padding with :0 Date: Thu, 12 Sep 2002 06:46:00 -0000 [thread overview] Message-ID: <20020912133930.20927.qmail@sources.redhat.com> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1651 bytes --] >Number: 7895 >Category: c >Synopsis: Bit-field initialization incorrect after padding with :0 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Sep 12 06:46:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Jörg Eckart >Release: Reading specs from /app/unido-inf/sun4_56/gcc/2.95.2/lib/gcc-lib/sparc-sun-solaris2.6/2.95.2/specsgcc version 2.95.2 19991024 (release) >Organization: >Environment: SunOS ls12so 5.8 Generic_108528-12 sun4u sparc SUNW,Sun-Blade-1000 >Description: The bit-field A::c in the example code should be initialized with 3 (instead of 0). When omitting the padding field or specifying another padding width than 0, c is initialized correctly. Further accesses to c are also done correctly. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="bitfield.c" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="bitfield.c" I2luY2x1ZGUgPHN0ZGlvLmg+CgpzdHJ1Y3QgQQp7CiAgdW5zaWduZWQgYToxOwogIHVuc2lnbmVk IGI6MjsKICB1bnNpZ25lZCA6MDsKICB1bnNpZ25lZCBjOjM7CiAgdW5zaWduZWQgOjI7CiAgdW5z aWduZWQgZDo0Owp9IGdsb2JBID0geyAxLCAyLCAzLCA0IH07Cgp2b2lkIG91dChzdHJ1Y3QgQSAq YSkKewogIHByaW50ZigiJXUsICV1LCAldSwgJXVcbiIsIGEtPmEsIGEtPmIsIGEtPmMsIGEtPmQp Owp9CgppbnQgbWFpbigpCnsKICAvLyBUZXN0IDE6IExvY2FsIGluaXRpYWxpemF0aW9uOgogIHN0 cnVjdCBBIGxvY0E9eyAxLCAyLCAzLCA0IH07CgogIG91dCgmbG9jQSk7IC8vIDEsIDIsIDMsIDQK CiAgb3V0KCZnbG9iQSk7IC8vIDEsIDIsIDMsIDQKCiAgcmV0dXJuIDA7Cn0K
reply other threads:[~2002-09-12 13:46 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020912133930.20927.qmail@sources.redhat.com \ --to=eckart@icd.de \ --cc=gcc-gnats@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).