Michael Hope wrote:
but this causes trouble when setting up ACC for the likes of the add
above. The compiler runs but the code is incorrect
Incorrect how? If you don't give us precise descriptions of the
problem, then we can't give you precise answers. A precise description
would be RTL e
Bonjour,
Faites votre publicité sur: http://www.saguenaylac.com
pour juste 20$/an ou 50$/3ans sur
le portail du Saguenay - Lac-Saint-Jean.
Nous concevons aussi des sites web à 200$ en moyenne.
Voir aussi nos modèles sur: http://www.flashblogg.com .
Merci beaucoup.
SaguenayLac.com
Hi there. The machine I'm working is part accumulator based, part
register based. I'm having trouble figuring out how best to tell the
compiler how ACC is affected and when.
For example, the add instruction is two operand with the destination
being a general register:
ADD, R11 is equivalent to
Snapshot gcc-4.5-20090521 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.5-20090521/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk
On Thu, May 21, 2009 at 11:11 AM, Ian Lance Taylor wrote:
> Richard Guenther writes:
>
>> On Thu, May 21, 2009 at 1:50 PM, Andreas Schwab
>> wrote:
>>> Ian Lance Taylor writes:
>>>
Consider this C/C++ program:
extern void **f1();
void f2(const char *p) { *(const void **)f1(
On Thu, May 21, 2009 at 5:20 AM, Richard Guenther
wrote:
> On Thu, May 21, 2009 at 7:10 AM, Ian Lance Taylor wrote:
>> Consider this C/C++ program:
>>
>> extern void **f1();
>> void f2(const char *p) { *(const void **)f1() = p; }
>>
>> If I compile this program with g++ -Wcast-qual, I get this:
>
On Thu, May 21, 2009 at 12:10 AM, Ian Lance Taylor wrote:
> Consider this C/C++ program:
>
> extern void **f1();
> void f2(const char *p) { *(const void **)f1() = p; }
>
> If I compile this program with g++ -Wcast-qual, I get this:
>
> foo2.cc:2: warning: cast from type ‘void**’ to type ‘const voi
Richard Guenther writes:
> On Thu, May 21, 2009 at 1:50 PM, Andreas Schwab wrote:
>> Ian Lance Taylor writes:
>>
>>> Consider this C/C++ program:
>>>
>>> extern void **f1();
>>> void f2(const char *p) { *(const void **)f1() = p; }
>>>
>>> If I compile this program with g++ -Wcast-qual, I get th
"Joseph S. Myers" writes:
> On Wed, 20 May 2009, Ian Lance Taylor wrote:
>
>> All that aside, I can't think of any reason that the C and C++ frontends
>> should be different in this regard. Does anybody want to make an
>
> There's the fairly obvious reason that C and C++ have different rules on
chenyang writes:
>> Try running your commands with the --save-temps options and compare the
>> resulting .s files. Also, try running the commands with the
>> -fdump-tree-all -fdump-rtl-all options and see where the dump files
>> first differ.
>>
> I tried --save-temps and the resulting .s files
> From: Andrew Pinski
> To: Jamie Prescott
> Cc: Ian Lance Taylor ; gcc@gcc.gnu.org
> Sent: Thursday, May 21, 2009 8:22:00 AM
> Subject: Re: nops
>
> On Thu, May 21, 2009 at 8:13 AM, Jamie Prescott wrote:
> > My target does not have anything special WRT alignment. I even set the
> function
>
On Thu, May 21, 2009 at 8:13 AM, Jamie Prescott wrote:
> My target does not have anything special WRT alignment. I even set the
> function
> alignment to 8, and it still issues gen_nop().
> This seem to happen only with -O0, or at least I noticed it only under such
> condition
> so far.
so it h
- Original Message
> From: Ian Lance Taylor
> To: Jamie Prescott
> Cc: gcc@gcc.gnu.org
> Sent: Wednesday, May 20, 2009 9:50:50 PM
> Subject: Re: nops
>
> Jamie Prescott writes:
>
> > Under which conditions GCC generates nops?
>
> It depends entirely on the target. For many targets,
Thanks for your advice.
Andy Vaught wrote on May 19:
I've got this fixed, your test code now compiles to 428 bytes. It's a
very osx-specific deal...
Thanks to Dominique Dhumieres for letting me know that
new versions were posted to ftp.g95.org:
-rw-r--r--2 2055 2055 3229447 May
Ian Lance Taylor wrote:
> Consider this C/C++ program:
>
> extern void **f1();
> void f2(const char *p) { *(const void **)f1() = p; }
>
> If I compile this program with g++ -Wcast-qual, I get this:
>
> foo2.cc:2: warning: cast from type ‘void**’ to type ‘const void**’ casts away
> qualifiers
>
Richard Guenther wrote:
> On Thu, May 21, 2009 at 1:50 PM, Andreas Schwab wrote:
>
>> Ian Lance Taylor writes:
>>
>>
>>> Consider this C/C++ program:
>>>
>>> extern void **f1();
>>> void f2(const char *p) { *(const void **)f1() = p; }
>>>
>>> If I compile this program with g++ -Wcast-qual
Richard Guenther writes:
> For
>
> extern const char **f1();
> void f(char *p)
> {
> *(char **)f1() = p;
> }
>
> it warns with
>
> t.C: In function ‘void f(char*)’:
> t.C:4: warning: cast from type ‘const char**’ to type ‘char**’ casts
> away constness
>
> which makes sense.
This is actually a
On Thu, May 21, 2009 at 1:50 PM, Andreas Schwab wrote:
> Ian Lance Taylor writes:
>
>> Consider this C/C++ program:
>>
>> extern void **f1();
>> void f2(const char *p) { *(const void **)f1() = p; }
>>
>> If I compile this program with g++ -Wcast-qual, I get this:
>>
>> foo2.cc:2: warning: cast fr
On Wed, 20 May 2009, Ian Lance Taylor wrote:
> All that aside, I can't think of any reason that the C and C++ frontends
> should be different in this regard. Does anybody want to make an
There's the fairly obvious reason that C and C++ have different rules on
implicit conversions involving cons
Status
==
The 4.4 branch is open under the usual release branch rules, a 4.4.1
release planned around June 21st. The branch seems to be in good
shape and new bugs still get fixed quickly. There are a few bugs
that I would block the 4.4.1 release for, including the reported
ICE building SPEC
Ian Lance Taylor writes:
> Consider this C/C++ program:
>
> extern void **f1();
> void f2(const char *p) { *(const void **)f1() = p; }
>
> If I compile this program with g++ -Wcast-qual, I get this:
>
> foo2.cc:2: warning: cast from type ‘void**’ to type ‘const void**’ casts away
> qualifiers
I
On Thu, May 21, 2009 at 7:10 AM, Ian Lance Taylor wrote:
> Consider this C/C++ program:
>
> extern void **f1();
> void f2(const char *p) { *(const void **)f1() = p; }
>
> If I compile this program with g++ -Wcast-qual, I get this:
>
> foo2.cc:2: warning: cast from type ‘void**’ to type ‘const void
Thanks, Ian,
> These kinds of issues are always difficult to debug. There have been a
> couple of patches to stabilize different sorts which I don't think are
> in 4.3.3. That could conceivably cause differences if address space
> randomization is turned on. I don't know of any specific bug rep
23 matches
Mail list logo
