Mark Polo wrote:
> hi im newbie to Linux platform .
>
This mailing list is for those who write and maintain gcc, not for those
asking questions about how to *use* it.
Please ask either on [EMAIL PROTECTED] or perhaps in a forum for java
related questions.
Also indicating the actual error you a
Hi,
I am writing instruction patterns for vector modes (V4Si, V8HI, V16QI,
etc). Since these modes have the same length, the underlying
instructions may also be the same (load/store instrucitons, AND/OR
instructions, etc). Is there any simple way to combines patterns for
different modes instead
Consider the following code:
f.cc ==>
void f(const unsigned char b)
{
unsigned char c = static_cast(b & 0xff);
}
<== f.cc
Compile with g++ 4.1.2:
$ g++-4.3-20071109 -c f.cc -Wconversion
$
Note no warnings.
Compile with g++ 4.3-20071109:
$ g++-4.3-20071109 -c f.cc -Wconversion
f.cc:
On 22 November 2007 14:30, Bingfeng Mei wrote:
> Hi,
>
> I am writing instruction patterns for vector modes (V4Si, V8HI, V16QI,
> etc). Since these modes have the same length, the underlying
> instructions may also be the same (load/store instrucitons, AND/OR
> instructions, etc). Is there any
Dave,
Is is only for 4.3+? Define_mode_iterator is not recognized in 4.2.1 I
am working on. And I didn't find anything in GCC4.2.1 internal manual
either.
Cheer.
Bingfeng
-Original Message-
From: Dave Korn [mailto:[EMAIL PROTECTED]
Sent: 22 November 2007 15:00
To: Bingfeng Mei; gcc@g
On 22 November 2007 15:30, Bingfeng Mei wrote:
> Dave,
> Is is only for 4.3+? Define_mode_iterator is not recognized in 4.2.1 I
> am working on. And I didn't find anything in GCC4.2.1 internal manual
> either.
Sorry, I don't know when they were first introduced, but if you can't find
them in
On 22/11/2007, Tom Browder <[EMAIL PROTECTED]> wrote:
> Compile with g++ 4.3-20071109:
>
> $ g++-4.3-20071109 -c f.cc -Wconversion
> f.cc: In function 'void f(unsigned char)':
> f.cc:3: warning: conversion to 'unsigned char' from 'int' may alter its
> value
>
> Is this a legitimate warning o
Mark Mitchell <[EMAIL PROTECTED]> writes:
> [...]
>> Who is "we"? What better debugging are GCC users demanding? What
>> debugging difficulties are they experiencing? Who is that set of users?
>> What functional changes would improve those cases? What is the cost of
>> those improvements
Benjamin Smedberg <[EMAIL PROTECTED]> writes:
> Diego Novillo wrote:
>> Before plug-ins: put your gimple-to-myIR converter in passes.c
>> After plug-ins: dlopen gimple-to-myIR.so
>>
>> Both represent the same effort. Both require your converter to be kept
>> up-to-date with GCC's ever shifting A
I can't seem to find a concrete answer anywhere to this: does the
current version of gcc support building executables for the 64 bit
version of Windows?
I am using gcc through MinGW and using the -m64 option results in a
"sorry, unimplemented: 64-bit mode not compiled in" message.
Thanks,
Ali.
On Nov 22, 2007 8:22 PM, Frank Ch. Eigler <[EMAIL PROTECTED]> wrote:
>
> Mark Mitchell <[EMAIL PROTECTED]> writes:
>
> > [...]
> >> Who is "we"? What better debugging are GCC users demanding? What
> >> debugging difficulties are they experiencing? Who is that set of users?
> >> What functio
On Nov 22, 2007 10:46 AM, Manuel López-Ibáñez <[EMAIL PROTECTED]> wrote:
> On 22/11/2007, Tom Browder <[EMAIL PROTECTED]> wrote:
> > Compile with g++ 4.3-20071109:
...
> There is something odd going on, so please open a bug report and add
> [EMAIL PROTECTED] to the CC list.
Done as requested, see
For this testcase:
void g(const unsigned char b)
{
unsigned short c = b & 0xff;
}
we get:
wconversion-3.c:3: warning: conversion to 'unsigned char' from 'int'
may alter its value
wconversion-3.c:3: warning: conversion to 'short unsigned int' from
'int' may alter its value
Really weird... It is
On Thu, Nov 22, 2007 at 07:30:08AM -0800, Bingfeng Mei wrote:
> Dave,
> Is is only for 4.3+? Define_mode_iterator is not recognized in 4.2.1 I
> am working on. And I didn't find anything in GCC4.2.1 internal manual
> either.
They used to be called "define_mode_macro" and "define_code_macro".
On Fri, Nov 23, 2007 at 12:02:31AM +0100, Manuel López-Ibáñez wrote:
> For this testcase:
>
> void g(const unsigned char b)
> {
> unsigned short c = b & 0xff;
> }
>
> we get:
>
> wconversion-3.c:3: warning: conversion to 'unsigned char' from 'int'
> may alter its value
> wconversion-3.c:3: warn
On Nov 22, 2007 8:30 PM, Joe Buck <[EMAIL PROTECTED]> wrote:
> On Fri, Nov 23, 2007 at 12:02:31AM +0100, Manuel López-Ibáñez wrote:
> > For this testcase:
...
> > unsigned short c = b & 0xff;
> The type of (b & 0xff) is int. However, the value is bounded, and must be
In a similar case with unsi
On Nov 22, 2007 2:55 PM, Ali, Muhammad <[EMAIL PROTECTED]> wrote:
> I can't seem to find a concrete answer anywhere to this: does the
> current version of gcc support building executables for the 64 bit
> version of Windows?
>
> I am using gcc through MinGW and using the -m64 option results in a
>
On 23/11/2007, Joe Buck <[EMAIL PROTECTED]> wrote:
> >
> > wconversion-3.c:3: warning: conversion to 'unsigned char' from 'int'
> > may alter its value
> > wconversion-3.c:3: warning: conversion to 'short unsigned int' from
> > 'int' may alter its value
>
> The type of (b & 0xff) is int. However,
Ali, Muhammad wrote:
> I can't seem to find a concrete answer anywhere to this: does the
> current version of gcc support building executables for the 64 bit
> version of Windows?
>
> I am using gcc through MinGW and using the -m64 option results in a
> "sorry, unimplemented: 64-bit mode not compi
19 matches
Mail list logo
