|
From: Mailing l. u. f. U. C. a. U. <kal...@li...> - 2013-07-25 15:21:38
|
On Thu, Jul 25, 2013 at 3:55 PM, Arnab Ghoshal <ar...@gm...> wrote:
> Well, the implicit casting of const char* to true is
> probably not guaranteed to work with every compiler.
Scratch that! I was just going over the icpc discussion thread you
pointed to. From the "non-integral operation not allowed in nontype
template argument" error message, I am guessing that icpc is not
treating '&& "string"' as a constant integral expression, which seems
to be wrong... unless I am missing something.
> Could you check
> if all the tests pass? Such && "error message" shows up in many places
> with KALDI_ASSERT. -Arnab
>
> On Thu, Jul 25, 2013 at 2:55 PM, Mailing list used for User
> Communication and Updates <kal...@li...> wrote:
>> Hi Vassil,
>>
>> Just found that
>> changing push-lattice.cc(line131) from
>>
>> KALDI_COMPILE_TIME_ASSERT(static_cast<StateId>(-1) <
>> static_cast<StateId>(0) &&
>> "This code only works if StateId is signed;
>> otherwise, fix.");
>>
>> to
>>
>> KALDI_COMPILE_TIME_ASSERT(static_cast<StateId>(-1) <
>> static_cast<StateId>(0));
>>
>> can solve problem.
>>
>>
>> KALDI_COMPILE_TIME_ASSERT() is acceptable to icpc if const char* (the error
>> msg) is not involved in the its argument.
>>
>> It seems KALDI_COMPILE_TIME_ASSERT() has been used many times in kaldi, and
>> only this one has a error msg like this {&& "blabla"}
>>
>>
>>
>> kangshiyin
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Kaldi-users mailing list
>> Kal...@li...
>> https://lists.sourceforge.net/lists/listinfo/kaldi-users
>>
|