Thanks for the quick response - the possibility of different modes seems
plausible, as I'm not sure what would happen in that case. (Although I'm not
entirely sure how that case would occur - something that may have changed since
the original.) I haven't had much luck in getting a working toolchai
On 06/26/14 14:13, Jeff Law wrote:
On 06/26/14 02:44, Bin.Cheng wrote:
Hi,
I ran into PR60947, in which GCC understands the return value of
memset is the first argument passed in, according to standard, then
does optimization like below:
movip, sp
stmfdsp!, {r4, r5, r6, r7, r8,
Using LTO to create a DSO works fine (i.e., it performs the expected
optimizations) for symbols which are marked with visibility
attributes. It does not work, though, when the symbol is not
restricted in its visibility in the source file but instead is
prevented from being exported from the DSO by
On Mon, 30 Jun 2014, Hebenstreit, Michael wrote:
> I tested from home to reach https://gcc.gnu.org/pub/gcc/infrastructure/
Well, that is not supposed to be there to begin with.
The original report was about links to
ftp://gcc.gnu.org/pub/gcc/infrastructure/
not working from https://gcc.gnu.or
