Displaying 10 results from an estimated 10 matches for "striclti".
Did you mean:
striclty
2002 Jan 09
1
Not striclty a bug but a problem (PR#1250)
Version: 1040
OS: Windows 98 SE
Problem:
I have installed R with all help files to a network read-only drive. help.start() requires rw on two files
../R/rw1040/doc/html/packages.html
../R/rw1040/doc/html/search/index.txt
This is a minor issue as running R 1.4.0 help from the start menu works fine.
Perhaps the next version may address this?
Simon Bowman
Systems Adminstrator
University of Bath
2005 Mar 08
5
Please help with install *
I'm a neewbie in Linux, so please bear with me.
I have a school assignment to make communication between 10 SIP softphones (kphone).
So far I got trouble installing Asterisk. The information in asterisk web site seems to be a bit outdated because it's mentioned only kernel 2.4.
Since Mandrake cooker (10.2beta3) witch I'm using is using kernel 2.6.10, I wander if I have a chance to
2016 Mar 25
3
RFC: New support for triaging optimization-related failures in front ends
And as we are on the topic of bisecting/diagnosing scripts I attached my personal script I used before.
You give it two directories with assembly files (typically from a known good compiler and a "bad" compiler). The script will then go on and create permutations by picking all files from the "good" directory and combining them with a single file form the "bad"
2016 Mar 26
2
RFC: New support for triaging optimization-related failures in front ends
Ok I cleaned it up and added some explaining comments. It's in llvm/utils/abtest now.
- Mathias
> On Mar 25, 2016, at 4:40 PM, Michael Gottesman <mgottesman at apple.com> wrote:
>
>
>> On Mar 25, 2016, at 4:37 PM, Matthias Braun <matze at braunis.de <mailto:matze at braunis.de>> wrote:
>>
>> And as we are on the topic of bisecting/diagnosing
2016 Mar 25
0
RFC: New support for triaging optimization-related failures in front ends
> On Mar 25, 2016, at 4:37 PM, Matthias Braun <matze at braunis.de> wrote:
>
> And as we are on the topic of bisecting/diagnosing scripts I attached my personal script I used before.
>
> You give it two directories with assembly files (typically from a known good compiler and a "bad" compiler). The script will then go on and create permutations by picking all files
2016 Mar 26
0
RFC: New support for triaging optimization-related failures in front ends
I've worked on a compiler with a counter, but for individual optimisations, not just passes. It was incredibly useful!
In the llvm world, it would let you bisect exactly which instcombine, dagcombine, or whatever causes an issue.
I support the addition of a pass counter if it helps bisecting, but just wanted to point out that this can be as fine grained as the community is willing to accept.
2016 Mar 28
2
RFC: New support for triaging optimization-related failures in front ends
I agree that the more fine grained this becomes the more useful it can be.
I’ve updated my prototype to use a single number approach. I’m going to clean this up and post a review in the next day or two.
-Andy
From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Pete Cooper via llvm-dev
Sent: Friday, March 25, 2016 10:22 PM
To: Matthias Braun <matze at braunis.de>
Cc:
2016 Apr 05
2
RFC: New support for triaging optimization-related failures in front ends
Hi Greg,
Thanks for your input!
I’d love to see this evolve into something that would let us track problems to individual IR changes. My thinking is that starting with passes gives us something that will get us maybe 70% of the functionality in one easy step, then individual passes can be instrumented as anyone has time or need to get us the rest of the way there.
Your max_opt option sounds
2016 Mar 25
0
RFC: New support for triaging optimization-related failures in front ends
I will describe the complete process for completeness thus hopefully forestalling all questions [tell me if I did not ; )]. There is not much to it TBH.
./utils/bisect is a dumb python script that allows for arbitrary bisecting via the exit status of a script it runs . The way you use it is you write a script (lets call it test.sh). Then you invoke:
./utils/bisect --start=N --end=M ./test.sh
2016 Mar 25
2
RFC: New support for triaging optimization-related failures in front ends
> In the swift-world we use utils/bisect + a single number all the time + extra verifications. It works really well.
Can you describe to me what you mean by that exactly?
Are you using the single number in the LLVM back end or somewhere else?
From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Michael Gottesman via llvm-dev
Sent: Friday, March 25, 2016 12:35 PM
To: