On 06/05/11 02:24, David Daney wrote:
> This happens because the libgcc unwinder cannot find unwinding
> information for the PC at the point of the SIGSEGV.
>
> However, we know that usually when we end up with a PC of zero, it is
> because we called through a NULL function pointer. In this ca
On 06/05/2011 09:00, Andreas Schwab wrote:
> Ian Lance Taylor writes:
>
>> The difference is that with -E the -o option is passed to cc1, whereas
>> without it the -o option is passed to the assembler or the linker. The
>> GNU assembler and linker both have the usual Unix behaviour of only
>> usi
On Fri, May 6, 2011 at 2:16 AM, Diego Novillo wrote:
> This merge brings the gimple-front-end branch up to 4.7. It needed
> some minimal adjustments, but things seem to be working. Sandeep,
> please make sure it does. You may need to rebase your patch before
> committing it.
>
I got the build
On Sat, May 7, 2011 at 16:50, Sandeep Soni wrote:
> I got the build working on my machine. So preliminarily things seem to
> be working. In case this merge brings our branch up to 4.7 should "gcc
> -v" be showing it? It is not currently.
Yes, gcc -v should show:
Using built-in specs.
COLLECT_G
Snapshot gcc-4.7-20110507 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.7-20110507/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk
Hi,
I found in gcc/config/arm/ieee754-df.S, the function __aeabi_d2uiz
converts double into unsigned integer and the function always return 0
if the double value is negative. for example the following codes:
---sample codes--
unsigned long ul;
double d = -1.1
