bdver1 cpu(bulldozer) support with dragonegg

Project Infrastructure LLVM Dev List Archives
#1

Hello,
if I compile with dragonegg and -march=native I get this message:
'bdver1' is not a recognized processor for this target (ignoring processor)
Is there any plan to support this cpu ?

Here the full example the source file doesn't matter.

gcc -s -static -Wall -O2 -march=native -fplugin=dragonegg.so
-fplugin-arg-dragonegg-enable-gcc-optzns pointer.c -o pointer
'bdver1' is not a recognized processor for this target (ignoring processor)

#2

Hi Jan,

if I compile with dragonegg and -march=native I get this message:
'bdver1' is not a recognized processor for this target (ignoring processor)

this is coming directly from LLVM which doesn't know about bulldozer yet.

Is there any plan to support this cpu ?

I don't know. Hopefully someone who knows something about this will comment.

Ciao, Duncan.

#3

Hi Jan,

if I compile with dragonegg and -march=native I get this message:
'bdver1' is not a recognized processor for this target (ignoring processor)

this is coming directly from LLVM which doesn't know about bulldozer yet.

Is there any plan to support this cpu ?

I don't know. Hopefully someone who knows something about this will comment.

I added a basic description for bdver1 and bdver2 in r145493.
LLVM doesn't know many of bulldozer's new instructions though.

- Ben

#4

I added a basic description for bdver1 and bdver2 in r145493.
LLVM doesn't know many of bulldozer's new instructions though.

Thanks Ben!

Ciao, Duncan.

#5

Duncan Sands <baldrick@free.fr> writes:

Is there any plan to support this cpu ?

I don't know. Hopefully someone who knows something about this will comment.

We have some bulldozer tunings we'll push back as soon as we can get
upgraded to 3.0. Might be a few months, though. In the meantime,
simply adding the target wouldn't be very difficult.

                          -Dave

#6

Benjamin Kramer <benny.kra@googlemail.com> writes:

#7

Better be quick! I am adding FMA4 and XOP now, and if you contribute code before I do, you can spare yourself some XOP merging.

- Jan

#8

Jan Sjodin <jan_sjodin@yahoo.com> writes:

Better be quick! I am adding FMA4 and XOP now, and if you contribute
code before I do, you can spare yourself some XOP merging.

Go ahead. We're not going to get there soon enough. :frowning:

                             -Dave

#9

That is too bad. :frowning: You can always review the patches, and if you see something that can be done better let me know.

- Jan

#10

Jan Sjodin <jan_sjodin@yahoo.com> writes:

That is too bad. :frowning: You can always review the patches, and if you see something that can be done better let me know.

I don't think there will be. We just did basic intrinsic stuff, no
fancy patterns.

                             -Dave