This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: BImode is treated as normal byte-wide mode and causes bug.

From: Paolo Bonzini <bonzini at gnu dot org>
To: Bingfeng Mei <bmei at broadcom dot com>
Cc: Claudiu Zissulescu <claziss at gmail dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
Date: Wed, 22 Dec 2010 15:54:46 +0100
Subject: Re: BImode is treated as normal byte-wide mode and causes bug.
References: <7FB04A5C213E9943A72EE127DB74F0ADA692C6F0DB@SJEXCHCCR02.corp.ad.broadcom.com> <AANLkTinGk+pyXiKBAFjEpck2E_BDcLkrk=Ec117Pevnt@mail.gmail.com> <4D120C2E.8050008@gnu.org> <7FB04A5C213E9943A72EE127DB74F0ADA692DD9535@SJEXCHCCR02.corp.ad.broadcom.com>

On 12/22/2010 03:43 PM, Bingfeng Mei wrote:

Thanks for letting me know this. Since only our target experiences such
issue, I guess no other processors have such requirements of manipulating
BImode. I can live with the workaround now.

Perhaps Blackfin, but it has a BI->SI extension instruction so it doesn't see this bug.

Paolo

Follow-Ups:
- Re: BImode is treated as normal byte-wide mode and causes bug.
  - From: Richard Henderson

References:
- BImode is treated as normal byte-wide mode and causes bug.
  - From: Bingfeng Mei
- Re: BImode is treated as normal byte-wide mode and causes bug.
  - From: Claudiu Zissulescu
- Re: BImode is treated as normal byte-wide mode and causes bug.
  - From: Paolo Bonzini
- RE: BImode is treated as normal byte-wide mode and causes bug.
  - From: Bingfeng Mei

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]