On 05/18/2015 02:05 AM, Umesh Kalappa wrote:
> Getting a bus/hard error for the below case ,make sense since ldm/stm
> expects the address to be word aligned .
> --with-pkgversion='Cisco GCC c4.7.0-p1' --with-cisco-patch-level=1
The FSF doesn't support gcc-4.7.0 anymore. Generally, we only suppo
Thank you all for the reply and appreciate elaborate summary .
~Umesh
On Mon, May 18, 2015 at 10:08 PM, Richard Earnshaw
wrote:
> On 18/05/15 17:18, Joey Ye wrote:
>> In this case ldm is loading at alignment address. It is just loaded
>> more than sizeof a. So it can be the bus that does not per
On 18/05/15 17:18, Joey Ye wrote:
> In this case ldm is loading at alignment address. It is just loaded
> more than sizeof a. So it can be the bus that does not permit
> accessing memory beyond address range of a. Such a case I don't
> believe compiler is doing wrong.
>
If a starts on a 4-byte al
In this case ldm is loading at alignment address. It is just loaded
more than sizeof a. So it can be the bus that does not permit
accessing memory beyond address range of a. Such a case I don't
believe compiler is doing wrong.
On Mon, May 18, 2015 at 4:50 PM, Richard Earnshaw
wrote:
> On 18/05/15
On 18/05/15 10:05, Umesh Kalappa wrote:
> Hi All,
>
> Getting a bus/hard error for the below case ,make sense since ldm/stm
> expects the address to be word aligned .
>
> bash-4.1$ cat test.c
> struct test
> {
> char c;
> int i;
> } __attribute__((packed));
>
> struct test a,b;
>
Hi All,
Getting a bus/hard error for the below case ,make sense since ldm/stm
expects the address to be word aligned .
bash-4.1$ cat test.c
struct test
{
char c;
int i;
} __attribute__((packed));
struct test a,b;
int main()
{
a =b ; //here compiler is not sure that a or
