On Sat, Aug 21, 2004 at 02:27:17PM -0500, Matthew Dempsky wrote:
> Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
>
> > On Sat, Aug 21, 2004 at 12:44:03AM -0500, Matthew Dempsky wrote:
> >> No warning, but the generated code seems incorrect (or at least a
> >> regression from 3.3) unless ((int *)&v
Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
> On Sat, Aug 21, 2004 at 12:44:03AM -0500, Matthew Dempsky wrote:
>> No warning, but the generated code seems incorrect (or at least a
>> regression from 3.3) unless ((int *)&val)[x] isn't the correct
>> portable way to access a vector element, but th
On Sat, Aug 21, 2004 at 12:44:03AM -0500, Matthew Dempsky wrote:
> No warning, but the generated code seems incorrect (or at least a
> regression from 3.3) unless ((int *)&val)[x] isn't the correct
> portable way to access a vector element, but there doesn't seem to be
> an alternative that I've be
Package: gcc-3.4
Version: 3.4.1-4sarge1
Severity: normal
I'm compiling the following code example under both gcc 3.3.4-2 and
3.4.1-4sarge1:
#include
typedef int v4si __attribute__ ((mode(V4SI)));
static void
print_v4si (const char * name, v4si val)
{
int x;
4 matches
Mail list logo