Bug 38674 - When storing in a register the address of a value contained in the same register, gcc 4.3.2 on ARM clobbers the register before saving its content on the stack.
Summary: When storing in a register the address of a value contained in the same regis...
Status: RESOLVED DUPLICATE of bug 44404
Alias: None
Product: gcc
Classification: Unclassified
Component: middle-end (show other bugs)
Version: 4.3.2
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords: wrong-code
Depends on:
Blocks:
 
Reported: 2008-12-30 16:12 UTC by Gilles Chanteperdrix
Modified: 2015-02-19 11:34 UTC (History)
5 users (show)

See Also:
Host:
Target: armeb-unknown-linux-gnueabi
Build:
Known to work:
Known to fail:
Last reconfirmed: 2009-03-16 23:38:45


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gilles Chanteperdrix 2008-12-30 16:12:50 UTC
When compiling the following code with -O2:

#include <stdio.h>

static unsigned long long __attribute__((noinline)) f(void *ptr, unsigned long long ull)
{
	register unsigned long __r2 __asm__ ("r2") = (unsigned long) (&ull);
	__asm__ __volatile__ ("" : "+r" (__r2));
	return * (unsigned long long *) __r2;
}

int main(void)
{
	fprintf(stderr, "f(NULL, 0): %Lu\n", f(NULL, 0));
	return 0;
}

we get the following warning:
/tmp/ccJNzMaH.s: Assembler messages:
/tmp/ccJNzMaH.s:21: Warning: source register same as write-back base

And when running the program on target, the printed return value of f is not 0.

A disassembly of f:
000083f4 <f>:
    83f4:       e24dd008        sub     sp, sp, #8      ; 0x8
    83f8:       e28d2008        add     r2, sp, #8      ; 0x8
    83fc:       e16220f8        strd    r2, [r2, #-8]!
    8400:       e8920003        ldm     r2, {r0, r1}
    8404:       e28dd008        add     sp, sp, #8      ; 0x8
    8408:       e12fff1e        bx      lr

shows that r2 seems to be clobbered before its value is saved on stack.
Comment 1 Gilles Chanteperdrix 2009-01-05 15:21:45 UTC
The following, even simpler test case:

unsigned long long f(unsigned long long ull)
{
        register unsigned long long *__r0 __asm__ ("r0") = &ull;
        __asm__ __volatile__ ("" : "+r" (__r0));
        return * __r0;
}

gives the same warning, and the following assembly code:

00000000 <f>:
   0:   e24dd008        sub     sp, sp, #8      ; 0x8
   4:   e28d0008        add     r0, sp, #8      ; 0x8
   8:   e16000f8        strd    r0, [r0, #-8]!
   c:   e8900003        ldm     r0, {r0, r1}
  10:   e28dd008        add     sp, sp, #8      ; 0x8
  14:   e12fff1e        bx      lr
Comment 2 Richard Earnshaw 2009-03-16 23:38:45 UTC
Confirmed.  We need a way to represent an early-clobber between a register and a memory-address with side-effects.
Comment 3 cbaylis 2015-02-19 11:34:29 UTC
This appears to have been fixed by r161920

2010-07-07  Bernd Schmidt  <bernds@codesourcery.com>

        PR rtl-optimization/44404
        * auto-inc-dec.c (find_inc): Avoid calling count_occurrences if
        possible, use reg_overlap_mentioned_p instead.

*** This bug has been marked as a duplicate of bug 44404 ***