Skip to contentSkip to conversation

WAW dependency messages

DISCUSSION Jesse Barnes 5 participants 8 messages Oct 15, 2003 – Oct 20, 2003

lore
Share & tools
lore
#0 lore raw

In case anyone's interested, I just found a gcc bugzilla bug for the dependency violation stuff that always gets printed when we compile the kernel. I've added some information to it. The bug number is 12287, and you can see the whole thing at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id287.

Jesse

#1 lore raw
Quoted 6 lines · Jesse Barnes

In case anyone's interested, I just found a gcc bugzilla bug for the dependency violation stuff that always gets printed when we compile the kernel. I've added some information to it. The bug number is 12287, and you can see the whole thing at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id287.

I am working on some DV problems in assembler. With the new assembler, there are fewer DV warnings when compiling 2.4.21 kernel. If someone sends me small asm testcases, I will look into them.

H.J.

#2 lore raw
In reply to Jesse Barnes
Quoted 11 lines · H. J. Lu
Quoted 6 lines · Jesse Barnes

In case anyone's interested, I just found a gcc bugzilla bug for the dependency violation stuff that always gets printed when we compile the kernel. I've added some information to it. The bug number is 12287, and you can see the whole thing at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id287.

I am working on some DV problems in assembler. With the new assembler, there are fewer DV warnings when compiling 2.4.21 kernel. If someone sends me small asm testcases, I will look into them.

There's a testcase in the bug, but what prompted me to look was all of the messages that get printed out when compiling a 2.6 kernel. Does binutils 2.14.90.0.6 contain the fixes you're talking about? That's what I'm using...

Thanks,
Jesse

#3 lore raw
In reply to Jesse Barnes
Quoted 9 lines · Jesse Barnes
Quoted 8 lines · H. J. Lu
Quoted 6 lines · Jesse Barnes

In case anyone's interested, I just found a gcc bugzilla bug for the dependency violation stuff that always gets printed when we compile the kernel. I've added some information to it. The bug number is 12287, and you can see the whole thing at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id287.

Quoted 5 lines
Quoted 3 lines

I am working on some DV problems in assembler. With the new assembler, there are fewer DV warnings when compiling 2.4.21 kernel. If someone sends me small asm testcases, I will look into them.

There's a testcase in the bug, but what prompted me to look was all of

That testcase should be fixed in the next binutils.

Quoted 1 line

the messages that get printed out when compiling a 2.6 kernel. Does

Kernel is a totally different issue. You can send me small asm testcases. I will see what I can do.

Quoted 3 lines

binutils 2.14.90.0.6 contain the fixes you're talking about? That's what I'm using...

I am working on 2.14.90.0.7 which should have the fix.

H.J.

#4 lore raw
In reply to Jesse Barnes
Quoted 1 line · H. J. Lu

That testcase should be fixed in the next binutils.

Great!

Quoted 2 lines

Kernel is a totally different issue. You can send me small asm testcases. I will see what I can do.

Ok.

Quoted 1 line

I am working on 2.14.90.0.7 which should have the fix.

Ok, I'll check that out when you release it and try to put together some test .s files if I see more failures.

Thanks,
Jesse

#5 lore raw
In reply to Jesse Barnes
Quoted 2 lines

Kernel is a totally different issue. You can send me small asm testcases. I will see what I can do.

Something as simple as:

        itc.i r18
        ;;
        ld8 r19=[r17]

Will generate
aa.S: Assembler messages:
aa.S:3: Warning: Use of 'ld8' violates RAW dependency 'DTC' (data) aa.S:1: Warning: This is the location of the conflicting usage

Oddly enough, "as test.S" doesn't have warning message, but "as -x test.S" does. gcc is execve with "as -x" which triggers the warning message.

- Ken

#6 lore raw
In reply to Jesse Barnes
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · H. J. Lu

HJ> Kernel is a totally different issue. You can send me small asm HJ> testcases. I will see what I can do.

Here is one that bugs me (adapted from fsys.S):

$ cat t.S
        mov psr.l = r2;;
        mov r25=ar.rnat
$ as -x t.S
/r/wailua/tmp/t.S: Assembler messages:
/r/wailua/tmp/t.S:3: Warning: Use of 'mov.m' violates RAW dependency 'PSR.si' (data)
/r/wailua/tmp/t.S:1: Warning: This is the location of the conflicting usage
$ as --version |head -1
GNU assembler 2.13.90 20030425

I think the warnings shows up because the assembler doesn't detect that we're reading ar.rnat, not ar.itc.

	--david
#7 lore raw
In reply to Jesse Barnes
Quoted 3 lines · Kenneth W

Oddly enough, "as test.S" doesn't have warning message, but "as -x test.S" does. gcc is execve with "as -x" which triggers the warning message.

GNU as only does DV checking if the -x option is specified.

The DV checking stuff was never properly finished. It should be enabled by default. And we should emit errors instead of warnings for provable DVs. However, if we did that, we would then have the problem that false positives from bugs would prevent the compiler from working. So we would have to add an option to disable DV checking and have the compiler emit it. But then we would have the problem that the compiler output would not get any DV checking from the assembler, which is a worse problem than what we have now. We really need to get the bugs fixed first, and then emit errors by default for DVs. I'm glad to see that HJ has time to work on these problems.

Signature · 1 line
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com