Bug 110813 - Using -msse illegally
Summary: Using -msse illegally
Status: RESOLVED FIXED
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (other bugs)
Version First Reported In: 3.0.0
Platform: Compiled Sources Linux
: NOR major
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-15 12:43 UTC by Nach
Modified: 2005-09-12 18:57 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nach 2005-08-15 12:43:14 UTC
Recent builds (2.4.1 and 3.0.0 tested) seem to always put in -msse into the
CFLAGS. Essentally once compiled valgrind will no longer work on a CPU which
isn't Pentium 3+ or Athlon XP+.

Once I removed the -msse from the Makefile, valgrind works on my Athlon
Thunderbird again.
Comment 1 Nach 2005-08-15 14:58:09 UTC
Oh forgot to add this earlier, uname -a gives me: 
Linux NachBox 2.6.11-1-k7 #1 Mon Jun 20 21:26:23 MDT 2005 i686 GNU/Linux
Comment 2 Tom Hughes 2005-08-15 15:15:14 UTC
The -msse is only used for some of the test suites - it is not added automatically when building valgrind itself so it shouldn't cause any problems unless you want to run the tests.
Comment 3 Vitaly Prapirny 2005-09-07 17:01:42 UTC
There are errors in configure script that explains such behaviour. CFLAGS variable not restored after mmx and sse checks so it contains last checked flag (-msse) after that checks. The fix is simple - add
   CFLAGS=$safe_CFLAGS
after mmx flag check and sse flag check.
Comment 4 Vitaly Prapirny 2005-09-07 17:03:14 UTC
Seems that this error doesn't exist in 3.0.1 (but still in 2.4.1).
Comment 5 Nicholas Nethercote 2005-09-12 18:57:16 UTC
We're unlikely to release a 2.4.2.  Since it's fixed in the 3.0.X line, I'm closing this bug.