Re: Help working out where GCC decides the size of 0xFFFFFFFF

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Apr 20, 2015 at 1:51 PM, Alex Brown <alex.g.brown@xxxxxxxxx> wrote:

> I think I am slowly narrowing down where the bad decision is being
> made. Seems an incorrect results comes from a call to:
>
> bool wi::fits_to_tree_p(const T &x, const_tree type)
>
> and more specifically the call to eq_p() after it does a zext
>
> I am not sure yet if the issue is in that call, or if the tree data is
> incorrectly formed going in, but at least for the time being I have
> some leads to follow.

So it turns out it was a bug in one of the instructions in my
simulator, so no problems with the GCC configuration.




[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux