Bug 311318 - ARM: "128-bit constant is not implemented" error message
Summary: ARM: "128-bit constant is not implemented" error message
Status: RESOLVED FIXED
Alias: None
Product: valgrind
Classification: Developer tools
Component: vex (show other bugs)
Version: 3.9.0.SVN
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-07 19:22 UTC by Mans Rullgard
Modified: 2013-03-05 10:37 UTC (History)
0 users

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

Attachments
Test case (278 bytes, text/x-asm)
2012-12-07 19:22 UTC, Mans Rullgard 		Details
Patch (600 bytes, patch)
2012-12-07 19:26 UTC, Mans Rullgard 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mans Rullgard 2012-12-07 19:22:20 UTC 
Created attachment 75687 [details]
Test case

Running the attached program under valgrind produces this output:

==24333== Memcheck, a memory error detector
==24333== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==24333== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==24333== Command: ./a.out
==24333== 
V128{0xFFFF}
vex: the `impossible' happened:
   128-bit constant is not implemented
vex storage: T total 59509608 bytes allocated
vex storage: P total 528 bytes allocated

valgrind: the 'impossible' happened:
   LibVEX called failure_exit().
==24333==    at 0x3805EC0C: report_and_quit (m_libcassert.c:235)
==24333==    by 0xE28D200F: ???

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable
==24333==    at 0x8434: ??? (in /tmp/a.out)
Comment 1 Mans Rullgard 2012-12-07 19:26:55 UTC 
Created attachment 75688 [details]
Patch

This patch makes the error go away. Not sure if it's the correct fix.
Comment 2 Julian Seward 2013-03-05 10:37:04 UTC 
Fixed, r2693.  Thanks for the patch.  I think it was not quite right
and could have caused you to miss possible uninitialised value errors
in obscure circumstances.