bugGNU Development Chain for 68HC11/68HC12 - Bugs: bug #8120, Clear a word is not atomic on...


You are not allowed to post comments on this tracker with your current authentication level.

bug #8120: Clear a word is not atomic on 68hc12

Submitted by:  Stephane Carrez <ciceron>
Submitted on:  Thu Mar 11 19:39:22 2004  
Category: gccSeverity: 4 - Important
Item Group: sw-bugStatus: Fixed
Privacy: PublicAssigned to: Stephane Carrez <ciceron>
Open/Closed: Closed

Sun Aug 29 20:00:24 2004, comment #1:

Fixed in r2.92.

Stephane Carrez <ciceron>
Project AdministratorIn charge of this item.
Thu Mar 11 19:39:22 2004, original submission:

From sssjjjnnn@comcast.net:

I noticed some strange behavior in gcc. The following code:

void myfunc() {
(volatile unsigned)0x8000 = 0;

Compiles to:

clr -32767
clr -32768

It seems that the compiler is converting a 2-byte volatile access into two
1-byte accesses, which is probably not a good idea. The command line I used
to compile is:

m6811-elf-g++.exe -S -mshort -m68hcs12 -fomit-frame -pointer -fno-rtti
-frename-registers -mlong-calls -O2 x.cc

Is there a way to tell the compiler that you want to do a 2-byte access,
e.g. with a movw?

-- Justin

Stephane Carrez <ciceron>
Project AdministratorIn charge of this item.


No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


CC list is empty


Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.


Please enter the title of George Orwell's famous dystopian book (it's a date):



Follow 2 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Sun Aug 29 20:00:24 2004ciceronStatusNone=>Fixed

Back to the top

Powered by Savane 3.1-cleanup1