Getting this today on updates:
%svn update
stty: standard input: Invalid argument
stty: standard input: Invalid argument
svn: Checksum mismatch for '.svn/text-base/tree-vrp.c.svn-base';
expected: '284237c8119d7910c47b9bbee2161731', actual:
'99646b12bbb393c78836b9c1097a6cf8'
I tried a couple (dis
gcc (x86) recently changed its behaviour when returning values shorter
than int. It used to sign extend, and now it doesn't.
short func2( short *size) { return *size; }
trunk:
func2:
pushl %ebp
movl%esp, %ebp
movl8(%ebp), %eax
movzwl (%eax), %eax
> What's up?
Well, I just checked out the whole trunk again and everything is fine.
So, probably some screw-up on my end.
Sorry for the noise.
-benjamin
Hello Brian,
How does this compare to GCC-XML?
http://www.gccxml.org/HTML/Index.html
- Doug
On Jan 4, 2008 10:42 AM, Brian M. Ames <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have substantially completed an extension that would allow dumps to be
> emitted as XML. I would like to contribute i
On Mon, Jan 07, 2008 at 06:32:08PM +, Andrew Haley wrote:
>
> So, what now? Can we even agree about what the psABI actually says
> about sign-extending result values? Was what we did before correct,
> or what we do now? I don't believe that it doesn't matter.
You can follow up with this th
The frontends here would prefer to just implement __builtin_expect_call
(fp,foo), and leave __builtin_expect as it is now. We don't see a need for
a polymorphic __builtin_expect, as we are worried about backwards
compatibility.
A question was raised: Are side effects in the second parameter guar
Snapshot gcc-4.1-20080107 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.1-20080107/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.1 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
