Re: [cfe-users] [cfe-dev] Issues Running Scan-build

[Lockhart, Jonathan (lockhaja) via cfe-users]

Alexey or Others,


So I did a fresh full build with the latest checkout of clang, LLVM, Visual 
Studio, and CMake. The ALL-BUILD completed successfully but unfortunately no 
where in the build repository do I see a command of scan-build-py. There is 
also no repository of build\tools\scan-build-py or 
build\tools\clang\tools\scan-build-py. I tried running the new version of the 
batch file for scan-build, located in build\bin, but unfortunately that fails, 
as the first line of that batch file just says perl -S scan-build, and there is 
nothing else in the file.


Regards,
Jon Lockhart
PhD Candidate - EE Systems
University of Cincinnati
lockh...@mail.uc.edu



From: Alexey Sidorin 
Sent: Friday, January 22, 2016 3:12 PM
To: Lockhart, Jonathan (lockhaja)
Cc: cfe-...@lists.llvm.org
Subject: Re: [cfe-dev] Issues Running Scan-build

Jonathan,

as I see from your command line, you are still using an old version of 
scan-build. Could you check if this problem is reproducible with the newest one?
AFAIR, you can use new scan-build with your clang so it is not necessary to 
build clang from repository.


22.01.2016 01:45, Lockhart, Jonathan (lockhaja) пишет:

Alexey,


Thanks for the input, that seems to have resolved the issue. Thanks for 
noticing that spelling error as well. Now that you mention it, and checking the 
change logs, I seem to remember that being an issue before, and I link I moved 
to a different use environment. In any case, I now get a message about the


C:\Users\lockhaja\build\tools\clang\tools\scan-build>perl -S scan-build -v -v 
-o "C:\Users\lockhaja_local\Desktop" 
--use-analyzer=C:\Users\lockhaja\build\bin\Debug\clang.exe gcc C:\main.c

The syntax of the command is incorrect.
scan-build: Using 'C:/Users/lockhaja/build/bin/Debug/clang.exe' for static 
analysis
scan-build: Emitting reports for this run to 
'C:/Users/lockhaja_local/Desktop/2016-01-21-1'.

'C:/Users/lockhaja/build/tools/clang/tools/scan-build/ccc-analyzer' is not 
recognized as an internal or external command, operable program or batch file.

scan-build: No bugs found.


I purposefully added a few bugs into the system, so I know scan-build should be 
locating those. Any thoughts on the "syntax of the command is incorrect" and 
"'C:/Users/lockhaja/build/tools/clang/tools/scan-build/ccc-analyzer' is not 
recognized as an internal or external command, operable program or batch file." 
messages that have appeared? I did check and the ccc-analyzer file appears to 
be complete and correct.

Regards,
Jon Lockhart
PhD Candidate - EE Systems
University of Cincinnati
lockh...@mail.uc.edu



From: Alexey Sidorin 
Sent: Thursday, January 21, 2016 5:14 PM
To: Lockhart, Jonathan (lockhaja)
Cc: cfe-...@lists.llvm.org
Subject: Re: [cfe-dev] Issues Running Scan-build

Hello Jonathan,

It seems like you are using an old version of scan-build. This issue should be 
fixed with commit 4415a4b58bd 
(https://github.com/llvm-mirror/clang/commit/4415a4b58bd561d85a7dff84f62778b675a98a09).
 I suggest you to update your scan-build to the newest version and check it 
again.

You can also try the newest Python version of scan-build (which is located in 
tools/scan-build-py).

And, BTW, '--user-analyzer' option in your cmdline should be corrected to 
'--use-analyzer'.



22.01.2016 00:32, Lockhart, Jonathan (lockhaja) via cfe-dev пишет:

Greetings,


Been a while since I emailed the list. Oddly enough I have run into an error 
with my scan-build installation it seems. I previously had it up and running 
for a project I was doing back in 2014, and that Fall was the last I touched 
it. I have come back to use it with the same build, nothing has changed on the 
machine I am using since 2014, and I am getting an error upon launching. Please 
see the first screenshot. I checked the scan-build perl file and it tells me 
that the getpwuid on line 35 is set to "Unknown." Screenshot 2 has the info 
from the scan-build file. Screenshot 3 has the command I am inputting and the 
perl command it is switching too for the command line.


Any assistance would be much appreciated and I do apologize if I am mailing the 
wrong list, it has been a while.


Regards,
Jon Lockhart
PhD Candidate - EE Systems
University of Cincinnati
lockh...@mail.uc.edu



___
cfe-dev mailing list
cfe-...@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev



___
cfe-users mailing list
cfe-users@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-users

Re: [cfe-users] [cfe-dev] Issues Running Scan-build

[Laszlo Nagy via cfe-users]

hey Jon,

i can say things a few words about the `scan-build-py`, because was my
commit in the repo. :) first of all, it is an initial commit. not yet a
complete replacement of the `scan-build` (the one written in Perl). that's
the reason why it is not installed by any build target... but if you try it
out and report your experience that's helpful. (to "install" you need to
put the `tools/scan-build-py/bin` dir into your `PATH` environment
variable) it comes with a `README.md` file, which describes the usage.

regards,
Laszlo

On Fri, Jan 29, 2016 at 5:39 AM, Lockhart, Jonathan (lockhaja) via cfe-dev <
cfe-...@lists.llvm.org> wrote:

> Alexey or Others,
>
>
> So I did a fresh full build with the latest checkout of clang, LLVM,
> Visual Studio, and CMake. The ALL-BUILD completed successfully but
> unfortunately no where in the build repository do I see a command of
> scan-build-py. There is also no repository of build\tools\scan-build-py or
> build\tools\clang\tools\scan-build-py. I tried running the new version of
> the batch file for scan-build, located in build\bin, but unfortunately that
> fails, as the first line of that batch file just says perl -S scan-build,
> and there is nothing else in the file.
>
>
> Regards,
> Jon Lockhart
> PhD Candidate - EE Systems
> University of Cincinnati
> lockh...@mail.uc.edu
>
>
> --
> *From:* Alexey Sidorin 
> *Sent:* Friday, January 22, 2016 3:12 PM
>
> *To:* Lockhart, Jonathan (lockhaja)
> *Cc:* cfe-...@lists.llvm.org
> *Subject:* Re: [cfe-dev] Issues Running Scan-build
>
> Jonathan,
>
> as I see from your command line, you are still using an old version of
> scan-build. Could you check if this problem is reproducible with the newest
> one?
> AFAIR, you can use new scan-build with your clang so it is not necessary
> to build clang from repository.
>
>
> 22.01.2016 01:45, Lockhart, Jonathan (lockhaja) пишет:
>
> Alexey,
>
>
> Thanks for the input, that seems to have resolved the issue. Thanks for
> noticing that spelling error as well. Now that you mention it, and checking
> the change logs, I seem to remember that being an issue before, and I link
> I moved to a different use environment. In any case, I now get a message
> about the
>
> C:\Users\lockhaja\build\tools\clang\tools\scan-build>perl -S scan-build -v
> -v -o "C:\Users\lockhaja_local\Desktop"
> --use-analyzer=C:\Users\lockhaja\build\bin\Debug\clang.exe gcc C:\main.c
> The syntax of the command is incorrect.
> scan-build: Using 'C:/Users/lockhaja/build/bin/Debug/clang.exe' for static
> analysis
> scan-build: Emitting reports for this run to
> 'C:/Users/lockhaja_local/Desktop/2016-01-21-1'.
>
> 'C:/Users/lockhaja/build/tools/clang/tools/scan-build/ccc-analyzer' is not
> recognized as an internal or external command, operable program or batch
> file.
> scan-build: No bugs found.
>
> I purposefully added a few bugs into the system, so I know scan-build
> should be locating those. Any thoughts on the "syntax of the command is
> incorrect" and
> "'C:/Users/lockhaja/build/tools/clang/tools/scan-build/ccc-analyzer' is not
> recognized as an internal or external command, operable program or batch
> file." messages that have appeared? I did check and the ccc-analyzer file
> appears to be complete and correct.
>
> Regards,
> Jon Lockhart
> PhD Candidate - EE Systems
> University of Cincinnati
> lockh...@mail.uc.edu
>
>
> --
> *From:* Alexey Sidorin  
> *Sent:* Thursday, January 21, 2016 5:14 PM
> *To:* Lockhart, Jonathan (lockhaja)
> *Cc:* cfe-...@lists.llvm.org
> *Subject:* Re: [cfe-dev] Issues Running Scan-build
>
> Hello Jonathan,
>
> It seems like you are using an old version of scan-build. This issue
> should be fixed with commit 4415a4b58bd (
> 
> https://github.com/llvm-mirror/clang/commit/4415a4b58bd561d85a7dff84f62778b675a98a09).
> I suggest you to update your scan-build to the newest version and check it
> again.
>
> You can also try the newest Python version of scan-build (which is located
> in tools/scan-build-py).
>
> And, BTW, '--user-analyzer' option in your cmdline should be corrected to
> '--use-analyzer'.
>
>
>
> 22.01.2016 00:32, Lockhart, Jonathan (lockhaja) via cfe-dev пишет:
>
> Greetings,
>
>
> Been a while since I emailed the list. Oddly enough I have run into an
> error with my scan-build installation it seems. I previously had it up and
> running for a project I was doing back in 2014, and that Fall was the last
> I touched it. I have come back to use it with the same build, nothing has
> changed on the machine I am using since 2014, and I am getting an error
> upon launching. Please see the first screenshot. I checked the scan-build
> perl file and it tells me that the getpwuid on line 35 is set to "Unknown."
> Screenshot 2 has the info from the scan-build file. Screenshot 3 has the
> command I am inputting and the perl command it is switching too for 

Re: [cfe-users] [cfe-dev] Issues Running Scan-build

[Laszlo Nagy via cfe-users]

hey Jon,

as i mentioned earlier, the `scan-build-py` is not installed by any target.
so, it will stay in your source/checkout repository. (and it will be change
in the future when the implementation will be mature enough to release.) at
this moment it's self contained and not depend on anything, so you can copy
that subdirectory wherever you like, just put the `bin` dir into your
`PATH`.

regards,
Laszlo

On Fri, Jan 29, 2016 at 10:43 AM, Lockhart, Jonathan (lockhaja) <
lockh...@mail.uc.edu> wrote:

> Laszlo,
>
> Thanks you for your response. So I noticed I did have to do a fresh build
> from scratch. Unfortunately there was an issue with my path so it was not
> picking up through python installation. That has since been corrected and
> CMake picked up python this time so it is currently building.
>
> Now you say it will be in "tools/scan-build-py/bin". Will this be in the
> build folder or the check out repository? In my previous build after
> updating I saw no usable scan-build file in those repositories in the build
> folder.
>
> Regards,
> Jon Lockhart
>
>
>
> Sent from my Verizon Wireless 4G LTE smartphone
>
>
>  Original message 
> From: Laszlo Nagy 
> Date: 01/28/2016 6:26 PM (GMT-05:00)
> To: "Lockhart, Jonathan (lockhaja)" 
> Cc: Alexey Sidorin , cfe-...@lists.llvm.org,
> cfe-users@lists.llvm.org
> Subject: Re: [cfe-dev] Issues Running Scan-build
>
> hey Jon,
>
> i can say things a few words about the `scan-build-py`, because was my
> commit in the repo. :) first of all, it is an initial commit. not yet a
> complete replacement of the `scan-build` (the one written in Perl). that's
> the reason why it is not installed by any build target... but if you try it
> out and report your experience that's helpful. (to "install" you need to
> put the `tools/scan-build-py/bin` dir into your `PATH` environment
> variable) it comes with a `README.md` file, which describes the usage.
>
> regards,
> Laszlo
>
> On Fri, Jan 29, 2016 at 5:39 AM, Lockhart, Jonathan (lockhaja) via cfe-dev
>  wrote:
>
>> Alexey or Others,
>>
>>
>> So I did a fresh full build with the latest checkout of clang, LLVM,
>> Visual Studio, and CMake. The ALL-BUILD completed successfully but
>> unfortunately no where in the build repository do I see a command of
>> scan-build-py. There is also no repository of build\tools\scan-build-py or
>> build\tools\clang\tools\scan-build-py. I tried running the new version of
>> the batch file for scan-build, located in build\bin, but unfortunately that
>> fails, as the first line of that batch file just says perl -S scan-build,
>> and there is nothing else in the file.
>>
>>
>> Regards,
>> Jon Lockhart
>> PhD Candidate - EE Systems
>> University of Cincinnati
>> lockh...@mail.uc.edu
>>
>>
>> --
>> *From:* Alexey Sidorin 
>> *Sent:* Friday, January 22, 2016 3:12 PM
>>
>> *To:* Lockhart, Jonathan (lockhaja)
>> *Cc:* cfe-...@lists.llvm.org
>> *Subject:* Re: [cfe-dev] Issues Running Scan-build
>>
>> Jonathan,
>>
>> as I see from your command line, you are still using an old version of
>> scan-build. Could you check if this problem is reproducible with the newest
>> one?
>> AFAIR, you can use new scan-build with your clang so it is not necessary
>> to build clang from repository.
>>
>>
>> 22.01.2016 01:45, Lockhart, Jonathan (lockhaja) пишет:
>>
>> Alexey,
>>
>>
>> Thanks for the input, that seems to have resolved the issue. Thanks for
>> noticing that spelling error as well. Now that you mention it, and checking
>> the change logs, I seem to remember that being an issue before, and I link
>> I moved to a different use environment. In any case, I now get a message
>> about the
>>
>> C:\Users\lockhaja\build\tools\clang\tools\scan-build>perl -S scan-build
>> -v -v -o "C:\Users\lockhaja_local\Desktop"
>> --use-analyzer=C:\Users\lockhaja\build\bin\Debug\clang.exe gcc C:\main.c
>> The syntax of the command is incorrect.
>> scan-build: Using 'C:/Users/lockhaja/build/bin/Debug/clang.exe' for
>> static analysis
>> scan-build: Emitting reports for this run to
>> 'C:/Users/lockhaja_local/Desktop/2016-01-21-1'.
>>
>> 'C:/Users/lockhaja/build/tools/clang/tools/scan-build/ccc-analyzer' is
>> not recognized as an internal or external command, operable program or
>> batch file.
>> scan-build: No bugs found.
>>
>> I purposefully added a few bugs into the system, so I know scan-build
>> should be locating those. Any thoughts on the "syntax of the command is
>> incorrect" and
>> "'C:/Users/lockhaja/build/tools/clang/tools/scan-build/ccc-analyzer' is not
>> recognized as an internal or external command, operable program or batch
>> file." messages that have appeared? I did check and the ccc-analyzer file
>> appears to be complete and correct.
>>
>> Regards,
>> Jon Lockhart
>> PhD Candidate - EE Systems
>> University of Cincinnati
>> lockh...@mail.uc.edu
>>
>>
>> --
>> *From:* Alexey Sidorin  
>> *Sent:* Thursday, January 21, 2016 5:14 PM
>> *To:* Lockhart

[cfe-users] Does Integrated Assembler need Output Operands listed as Clobbered?

[Jeffrey Walton via cfe-users]

We have a user reporting a crash under Apple's Clang 7.0.2. The code is:

   __asm__ volatile(
#if BOOL_X64 || BOOL_X32
".byte 0x48, 0x0f, 0xc7, 0xf0;\n"  // rdrand rax
#else
".byte 0x0f, 0xc7, 0xf0;\n"// rdrand eax
#endif
"setc %1; "
: "=a" (val), "=qm" (rc)
:
: "cc"
);

The byte instructions are the op-codes for 'rdrand' instruction. Apple
Clang was late to provide them, so we have an implementation
regardless of downlevel compilers. They are also available for
downlevel GCC compilers in a hosted environment where the iron
provides a modern CPU.

The same user reports adding EAX or RAX as a clobber clears the issue.

Does Clang's Integrated Assembler need Output Operands listed as Clobbered?

Thanks in advance.
___
cfe-users mailing list
cfe-users@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-users