From: Peter Hurley <peter@hurleysoftware.com>
To: Alex Deucher <alexdeucher@gmail.com>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: bitfield structures
Date: Thu, 16 Oct 2014 11:57:18 -0400 [thread overview]
Message-ID: <543FEADE.1010407@hurleysoftware.com> (raw)
In-Reply-To: <CADnq5_MNf4L2eqe0xA7dwLMj=4zfL3UsO_H9cvJMQfz93FUOeA@mail.gmail.com>
On 10/16/2014 10:14 AM, Alex Deucher wrote:
> Are there any strong objections to these sorts of structures?
You may want to blacklist certain compiler version/arch combinations,
or get the affected arches to do it.
gcc up to 4.7.1 on ia64 and ppc64 generates 64-bit wide RMW cycles
on bitfields, regardless of the specified type or actual field width.
The enlarged write overwrites adjacent fields.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52080
Regards,
Peter Hurley
next prev parent reply other threads:[~2014-10-16 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 14:14 bitfield structures Alex Deucher
2014-10-16 15:33 ` Jerome Glisse
2014-10-16 15:57 ` Peter Hurley [this message]
2014-10-16 15:57 ` Eric Anholt
2014-10-16 19:16 ` Christian König
2014-10-16 21:14 ` Dave Airlie
2014-10-17 8:55 ` Michel Dänzer
2014-10-17 11:19 ` Rob Clark
2014-10-17 15:00 ` Alex Deucher
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=543FEADE.1010407@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.