[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [valgrind] [Bug 332917] Valgrind should warn the user that SSE4 is not supported in the 32-bit mode
From:       Philippe Waroquiers <philippe.waroquiers () skynet ! be>
Date:       2014-04-01 20:11:40
Message-ID: bug-332917-17878-c9w9tKlXrJ () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=332917

Philippe Waroquiers <philippe.waroquiers@skynet.be> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |philippe.waroquiers@skynet.
                   |                            |be

--- Comment #1 from Philippe Waroquiers <philippe.waroquiers@skynet.be> ---
(In reply to comment #0)
> So, don't you think that it's a good idea to warn the user that such
> instructions are not handled in 32-bit mode or just specify this information
> on official valgrind site? Some people would be grateful for such
> notifications :)
Yes, that looks a good idea.
Where could we put that, so that it is (likely to be) found by people needing
this info ?

From what I can see, the fact that SSE4 is not (fully) supported on 32 bits is
*already*
in the user manual (and so, also on the valgrind website, which has a copy
of the manual) :
  The 32 bits limited to SSE3  is in the first paragraph of the 'Limitations'
section:
  http://www.valgrind.org/docs/manual/manual-core.html#manual-core.limits
It is also somewhat documented in the NEWS file (search for SSE4).

Maybe we could put a reference to the FAQ and the user manual limitation in the
error msg:
#define M(a) VG_(umsg)(a "\n");
   M("Your program just tried to execute an instruction that Valgrind" );
   M("did not recognise.  There are two possible reasons for this."    );
   M("1. Your program has a bug and erroneously jumped to a non-code"  );
   M("   location.  If you are running Memcheck and you just saw a"    );
   M("   warning about a bad jump, it's probably your program's fault.");
   M("2. The instruction is legitimate but Valgrind doesn't handle it,");
   M("   i.e. it's Valgrind's fault.  If you think this is the case or");
   M("   you are not sure, please let us know and we'll try to fix it.");
   M("Either way, Valgrind will now raise a SIGILL signal which will"  );
   M("probably kill your program."                                     );
#undef M

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]