e 'double'
test.c:7: warning: 'var' is used uninitialized in this function
But the last one goes away if the first fprintf is commented out. So
gcc passes _something_ for var to fprintf, but what?
Thanks,
David Mathog
mat...@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech
y signature is that function from the start down to the DEBUGB
line with all lines present - sorry about the wrap:
David Mathog
mat...@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech
-
static int
forward_engine(i
endor_id : AuthenticAMD
cpu family : 15
model : 33
model name : Dual Core AMD Opteron(tm) Processor 280
stepping: 2
cpu MHz : 1000.000
cache size : 1024 KB
physical id : 0
siblings: 2
Is there something wrong with this program or is this a compiler bug?
Thanks,
David Mathog
mat...@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech
pproach seems to be just a different a way to spin the
pointer operations. For gcc in particular, is one approach or the other
to be preferred and why?
Thanks,
David Mathog
mat...@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech
__m128i __B)
{
return (~__A) & __B;
}
becomes
#define _mm_andnot_si128(A,B) (~A & B)
That approach will get really messy for the more complicated _mm*.
In general terms, can somebody give me a hint as to the sorts of things
that if found in inlined functions might cause the comp
A0908
DEBUG i 0
DEBUG masks[i] 0
DEBUG val1.ll [masks[i]] 706050403020100
Aborted
True enough 3020100 != 706050403020100, but what kind of test
is that???
Regards,
David Mathog
mat...@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech
#x27;
/root/tmp/ccYAq3IB.o: In function `sse2_test':
sse2-vec-4.c:(.text+0x58c): undefined reference to
`__builtin_ia32_vec_ext_v8hi'
.
.
.
/root/tmp/ccYAq3IB.o:sse2-vec-4.c:(.text+0x613): more undefined
references to `__builtin_ia32_vec_ext_v8hi' follow
collect2: ld returned 1 exit sta
Specifics on the environment where the problem is seen:
OS: Mandriva Linux release 2010.0 (Official) for x86_64
gcc (GCC) 4.4.1
Dual Dual Core Opteron 280.
Arima HDAMAI motherboard.
64 bit targets only, 32 bit is OK.
Regards,
David Mathog
mat...@caltech.edu
Manager, Sequence Analysis Facility
here (retrieve only directory, no
directory listings in pickup):
http://saf.bio.caltech.edu/pub/pickup/gccprob.tar.gz
I am not an assembler programmer. If one of you who is could have a
look at the two .s files maybe we can get to the bottom of this.
Thanks,
David Mathog
mat...@caltech.edu
e wrong values for s2 onto the call stack.
Bizarre. Either I'm missing something or turning off SSE2 is uncovering
a compiler bug.
Thanks,
David Mathog
mat...@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech
ck-boundary=4
3 -mincoming-stack-boundary=4
4 2 and 3
5 1 and 2 and 3
I guess the bigger question is why can an __m128d be passed on the call
stack reliably when -msse2 is invoked, but not otherwise? If the
compiler cannot do this reliably shouldn't it throw an error or warning?
Thank
00 41124.234000
test s1.xDEBUG m_d_fd: 1234.635654 2134.334300
test s2.xDEBUG m_d_fd: 2344.235400 41124.234000
IN _mm_add_pd
__ADEBUG m_d_fd: 1234.635654 2134.334300
__BDEBUG m_d_fd: 2344.235400 41124.234000
s1.xDEBUG m_d_fd: 1234.635654 2134.334300
s2.xDEBUG m_d_fd: 2344.235400 41124.234000
expected e0 e1 3578.871054 43258.568300
result r0 r1 3578.871054 43258.568300
Regards,
David Mathog
mat...@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech
hout errors
or warnings.
gcc --version is: gcc (GCC) 4.2.3 (4.2.3-6mnb1)
What does that compiler error mean?
Thanks,
David Mathog
mat...@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech
n phase of compilation?
Thank you,
David Mathog
mat...@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech
the right direction?
Thank you,
David Mathog
mat...@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech
15 matches
Mail list logo