Displaying 7 results from an estimated 7 matches for "iserr".
Did you mean:
is_err
2013 Nov 23
0
[LLVMdev] [RFC] Identifying access to errno
...(not sure I
agree with this).
1. Assume that all unknown external functions might read/write errno
2. Assume that all i32 pointers might point to errno (although we might be
> able to do better by somehow leveraging TBAA for "int"?)
>
Something like "MayBeErr", "IsErr", "IsntErr".
Does anyone see any problems with making stronger (type-based) assumptions
> re: errno (and, thus, on what things may alias with calls to
> errno-setting-libm functions)?
I don't, but I'm trying to think of a way to disable it if we know it's
"...
2013 Nov 23
2
[LLVMdev] [RFC] Identifying access to errno
...> 1. Assume that all unknown external functions might read/write errno
>
> 2. Assume that all i32 pointers might point to errno (although we
> might be able to do better by somehow leveraging TBAA for "int"?)
>
>
>
> Something like "MayBeErr", "IsErr", "IsntErr".
On what?
>
>
>
>
>
> Does anyone see any problems with making stronger (type-based)
> assumptions re: errno (and, thus, on what things may alias with
> calls to errno-setting-libm functions)?
>
>
> I don't, but I'm trying...
2013 Nov 23
2
[LLVMdev] [RFC] Identifying access to errno
Hello,
On some systems (Linux/glibc, for example), some libm math functions (like cos(double)) might set errno. It is important that we model this, in general, to prevent miscompilation (we would not, for example, want to reorder a call to cos in between a call to open and a call to perror). However, almost no code in the wild checks errno after calls to libm math functions, and this
2013 Nov 23
3
[LLVMdev] [RFC] Identifying access to errno
...read/write errno
>> >
>> > 2. Assume that all i32 pointers might point to errno (although we
>> > might be able to do better by somehow leveraging TBAA for "int"?)
>> >
>> >
>> >
>> > Something like "MayBeErr", "IsErr", "IsntErr".
>>
>> On what?
>>
>> >
>> >
>> >
>> >
>> >
>> > Does anyone see any problems with making stronger (type-based)
>> > assumptions re: errno (and, thus, on what things may alias with
>> &...
2013 Nov 23
0
[LLVMdev] [RFC] Identifying access to errno
...wn external functions might read/write errno
> >
> > 2. Assume that all i32 pointers might point to errno (although we
> > might be able to do better by somehow leveraging TBAA for "int"?)
> >
> >
> >
> > Something like "MayBeErr", "IsErr", "IsntErr".
>
> On what?
>
> >
> >
> >
> >
> >
> > Does anyone see any problems with making stronger (type-based)
> > assumptions re: errno (and, thus, on what things may alias with
> > calls to errno-setting-libm functions)?...
2013 Nov 24
0
[LLVMdev] [RFC] Identifying access to errno
...nctions might read/write
> > errno
> >
> > 2. Assume that all i32 pointers might point to errno (although we
> > might be able to do better by somehow leveraging TBAA for "int"?)
> >
> >
> >
> > Something like "MayBeErr", "IsErr", "IsntErr".
>
> On what?
>
>
> >
> >
> >
> >
> >
> > Does anyone see any problems with making stronger (type-based)
> > assumptions re: errno (and, thus, on what things may alias with
> > calls to errno-setting-libm...
2013 Nov 24
1
[LLVMdev] [RFC] Identifying access to errno
...gt; errno
> > >
> > > 2. Assume that all i32 pointers might point to errno (although we
> > > might be able to do better by somehow leveraging TBAA for "int"?)
> > >
> > >
> > >
> > > Something like "MayBeErr", "IsErr", "IsntErr".
> >
> > On what?
> >
> >
> > >
> > >
> > >
> > >
> > >
> > > Does anyone see any problems with making stronger (type-based)
> > > assumptions re: errno (and, thus, on what things may a...