[erlang-questions] R12B-1 dialyzer 'Unsupported primop' error
John Webb
jwebb@REDACTED
Tue Mar 4 16:10:58 CET 2008
Many thanks for the clarification! I was curious as to whether it
was unsupported as in "overlooked" or unsupported as in "don't hold
your breath". I'll ignore old_style and breath normally :)
Best Regards,
John
On Mar 4, 2008, at 4:56 AM, Kostis Sagonas wrote:
> John Webb wrote:
>> In R12B-1 the following seemingly correct (if not so useful)
>> program yields the error {'Unsupported primop',
>> bs_context_to_binary} when dialyzer runs with the "Old Style"
>> analysis option.
>> -module(test).
>> -compile(export_all).
>> start(<<>>) -> ok.
>> The compiler seems to emit the primop when the function arguments
>> contain a binary match and there is no final catch-all clause. My
>> code runs as expected so I am assuming this is a dialyzer issue?
>
> Yes. The issue is that "old_style" has not been updated to support
> all primops that the current compiler generates. Come to think of
> it, why should it? We see little reason for a user to want
> "old_style" and at the same time generating .beam files by using the
> current compiler...
>
> Unrelated to your mail, last week we decided to discontinue support
> for the "old_style" option and today we actually took it out all
> that code.
> The current development version of Dialyzer spits out this error:
>
> Option --old_style is no longer supported
>
> Sorry, but there will not be a fix for your problem. The new
> Dialyzer is much much better and we see little reason to continue
> generating warnings without line information (as --old_style does).
>
> Kostis
More information about the erlang-questions
mailing list