You can get much better code if you make xrci a bit field.
so the entire bit filed region can be accessed word-wise:
#include
struct Xrb
{
uint16_t xrlen; /* Length of I/O buffer in bytes */
uint16_t xrbc; /* Byte count for transfer */
void * xrloc;
> On Jul 6, 2018, at 6:18 AM, Bernd Edlinger wrote:
>
> You can get much better code if you make xrci a bit field.
> so the entire bit filed region can be accessed word-wise:
>
>
> #include
>
> struct Xrb
> {
>uint16_t xrlen; /* Length of I/O buffer in bytes */
>uint16_
On Fri, Jul 06, 2018 at 11:14:41AM +1200, Soul Studios wrote:
> Simply because a struct has a constructor does not mean it isn't a
> viable target/source for use with memcpy/memmove/memset.
> Having benchmarked the alternatives memcpy/memmove/memset definitely
> makes a difference in various scen
On 07/06/2018 12:14 AM, Soul Studios wrote:
> Having benchmarked the alternatives memcpy/memmove/memset definitely makes a
> difference in various scenarios.
That sounds like a missing optimization in the compiler. If you have valid
testcases, I think it would be a good idea to file them in bugz
On 07/05/2018 05:14 PM, Soul Studios wrote:
Simply because a struct has a constructor does not mean it isn't a
viable target/source for use with memcpy/memmove/memset.
As the documentation that Segher quoted explains, it does
mean exactly that.
Some classes have user-defined copy and default c
Hello,
Are you interested in Accounting Software Users Contact Information? We can
also help you reach out to other Specialist as well.
We also provide:
ü QuickBooks Users
ü Financial Analytical Applications Users
ü Ecommerce Users
ü Configure Price Quote (CPQ) Users
Co
Snapshot gcc-8-20180706 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/8-20180706/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 8 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-8
