From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0002019]: Build fails on pcm_dmix.c
Date: Fri, 14 Apr 2006 18:01:13 +0200 [thread overview]
Message-ID: <6cdeb87666dec05377bb5cbd85178fd4@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2019>
======================================================================
Reported By: GrueMaster
Assigned To:
======================================================================
Project: ALSA - lib
Issue ID: 2019
Category: 1_pcm - digital audio
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 04-14-2006 01:00 CEST
Last Modified: 04-14-2006 18:01 CEST
======================================================================
Summary: Build fails on pcm_dmix.c
Description:
Build output:
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I../../include -g -O2 -MT
pcm_dmix.lo -MD -MP -MF .deps/pcm_dmix.Tpo -c pcm_dmix.c -fPIC -DPIC -o
.libs/pcm_dmix.o
/tmp/ccJTuE56.s: Assembler messages:
/tmp/ccJTuE56.s:209: Error: `(%ecx,%eax,1)' is not a valid 64 bit
base/index expression
/tmp/ccJTuE56.s:385: Error: `(%ecx,%eax,1)' is not a valid 64 bit
base/index expression
linux:/usr/src/alsa # gcc -v
Reading specs from /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/specs
Configured with: ../configure --enable-threads=posix --prefix=/usr
--with-local-prefix=/usr/local --infodir=/usr/share/info
--mandir=/usr/share/man --enable-languages=c,c++,f77,objc,java,ada
--disable-checking --libdir=/usr/lib64 --enable-libgcj
--with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib64
--with-system-zlib --enable-shared --enable-__cxa_atexit
x86_64-suse-linux
Thread model: posix
gcc version 3.3.3 (SuSE Linux)
Tested on RedHat Enterprise Desktop 4 update 2 - builds ok.
======================================================================
----------------------------------------------------------------------
GrueMaster - 04-14-06 18:01
----------------------------------------------------------------------
Compiler apparently has an issue with the pcm_dmix_x86_64.h inline assembly
macro MIX_AREAS3. The line in the macro is:
291: "\tleal (%%ecx,%%eax,1), %%ecx\n"
Issue History
Date Modified Username Field Change
======================================================================
04-14-06 01:00 GrueMaster New Issue
04-14-06 18:01 GrueMaster Note Added: 0009285
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next reply other threads:[~2006-04-14 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 16:01 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-14 16:30 [ALSA - lib 0002019]: Build fails on pcm_dmix.c bugtrack
2006-04-13 23:00 bugtrack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6cdeb87666dec05377bb5cbd85178fd4@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.