Displaying 7 results from an estimated 7 matches for "viva64".
Did you mean:
ia64
2016 Oct 31
2
PVS-Studio analysis of LLVM code
Hi!
Company behind PVS-Studio analyzed relatively recent version of LLVM
and some results are reported in http://www.viva64.com/en/b/0446/.
Eugene.
2017 Jan 15
3
unsigned int and FLAC__uint32 are used interchangeably
lvqcl wrote:
> Also MSVC fails because src/libFLAC/include/private/bitmath.h now
> contains "uint32_t long idx" instead of "unsigned long idx".
Ah, missed that because it was MSVC code. They should be `uint64_t`.
> According to MSDN _BitScanReverse*() functions have signatures:
> unsigned char _BitScanReverse(unsigned long *, unsigned long);
> unsigned char
2017 Jan 15
2
unsigned int and FLAC__uint32 are used interchangeably
lvqcl wrote:
> > Ah, missed that because it was MSVC code. They should be `uint64_t`.
>
> No, sizeof(unsigned long) is always 4 on Windows.
> See http://www.viva64.com/en/t/0012/
Bah! Trust Windows to be different :).
> >> According to MSDN _BitScanReverse*() functions have signatures:
> >> unsigned char _BitScanReverse(unsigned long *, unsigned long);
> >> unsigned char _BitScanReverse64(unsigned long *, unsigned __int64);
> &...
2016 Nov 01
3
PVS-Studio analysis of LLVM code
Hi, Jonas!
On Tue, Nov 1, 2016 at 3:26 AM, Jonas Wagner <jonas.wagner at epfl.ch> wrote:
> Hi Eugene,
>
> I think this is really cool! You've convinced me to try out PVS on some of
> my own projects :)
>
> Of all the warnings presented in the article, there was one for which I
> thought it's a false positive. By default, LLVM is compiled without RTTI and
>
2015 Mar 04
2
[LLVMdev] Google Summer of Code
Please provide a patch to Open Projects list.
On Wed, Mar 4, 2015 at 8:25 PM, Vassil Vassilev <vvasilev at cern.ch> wrote:
> On 17/02/15 09:47, Anton Korobeynikov wrote:
>>
>> John,
>>
>> Yes, I'm taking care about application as usual.
>
> I saw the the LLVM mentoring org was accepted. Congrats!
> Anton, could you tell me what is the procedure of
2015 Mar 09
2
[LLVMdev] Google Summer of Code
+Easily, some of the code snippets end up being copied dozens of
+times, which leads to worse maintainability, understandability and logical
+design.
The project description stresses code maintainability and logical design more than bug finding due to omissions in copy and pasted code. Reading this made me think of a check that would suggest people to replace copy and pasted code with a function
2015 Mar 11
2
[LLVMdev] Google Summer of Code
> On Mar 11, 2015, at 2:14 AM, Vassil Vassilev <vvasilev at cern.ch> wrote:
>
> On 10/03/15 19:13, Anna Zaks wrote:
>>
>>> On Mar 10, 2015, at 1:03 AM, Vassil Vassilev <vvasilev at cern.ch <mailto:vvasilev at cern.ch>> wrote:
>>>
>>> On 09/03/15 21:52, Anna Zaks wrote:
>>>>
>>>> +Easily, some of the code