Svadev mailing list

[Will Dietz <willdtz AT gmail.com>]

We might want to explore if there's a better way to handle this
ourselves (push all configuration to env values, instead of a
configure-time-style foo.in var replacement?), but anyway give this a
go:

cd $(SC_OBJ_DIR)/test
make clean
make lit ENABLE_OPTIMIZED=0 DISABLE_ASSERTIONS=0

Note that I only had to do this when I built my llvm/safecode tree in
a configuration that isn't what I specified when I ran configure. When
I configure llvm with --disable-optimized --enable-assertions, nothing
is needed here.

FWIW if you recently *changed* your configuration (and re-used a
safecode object tree) I don't think we'll update the testing values
properly, so that could be it.  But a fresh build configured
consistently should work.

Let us know if this resolves the issue for you, and if not any
additional details on your setup would be useful.

Thanks!

~Will

On Mon, Dec 12, 2011 at 3:39 PM, Santosh Nagarakatte
<santoshn AT cis.upenn.edu>
 wrote:
> I just have a Debug+Asserts build.
>
> Santosh
>
> On 12/12/2011 04:25 PM, Matthew Wala wrote:
>> On Mon, Dec 12, 2011 at 2:31 PM, Santosh Nagarakatte
>> <santoshn AT cis.upenn.edu>
>>  wrote:
>>> Hi all,
>>>
>>> I have Debug+Asserts build of llvm-3.0 and safecode from the trunk
>>> with revision 146398.
>>>
>>> However the litmus tests in safecode/test/  files always use the
>>> Release+Asserts build of clang.
>>>
>>> I am trying to run the litmus test with
>>> make ENABLE_OPTIMIZED=0 lit
>>>
>>> I see that it uses the BUILDMODE variable to determine the build type
>>> in the makefile at safecode/test/. However I was not able to figure
>>> out where the BUILDMODE was set.
>>>
>>> How do I make the litmus tests to use the Debug+Asserts build of SafeCode?
>>
>> BuildMode is set by llvm's Makefile.rules.
>> I've encountered a similar issue before. I think it was due to the
>> fact that I had multiple builds of different type in the same object
>> tree (I don't know if that's supported or not. If it is, then the
>> behavior you're encountering is a SAFECode bug.) Are you sure that
>> your object trees have only been used to build Debug+Asserts versions
>> of llvm and SAFECode?
>>
>> Matt
>>
>>> Thanks,
>>> Santosh
>>>
>>> --
>>> Santosh G Nagarakatte,
>>> PhD Student,
>>> Computer and Information Science Department
>>> University of Pennsylvania,
>>> Philadelphia-19104
>>> http://www.cis.upenn.edu/~santoshn
>>> _______________________________________________
>>> svadev mailing list
>>> svadev AT cs.uiuc.edu
>>> http://lists.cs.uiuc.edu/mailman/listinfo/svadev
>
> _______________________________________________
> svadev mailing list
> svadev AT cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/svadev