similar to: How to write an 'expected failure test'

There is already 10 PRs sent to GitHub repo. But they all are useless, in every PR people are being informed that they should send patches to http://reviews.llvm.org/

The "Revert [tag] message" is the default message generated by the 'git revert' command. Of course you would have to be using a git clone of LLVM instead of an SVN checkout in order to run 'git revert'. This command is the equivalent of 'svn merge –r' run from the top-level directory. I believe svn commands will operate only on the directories below the current

Hi, It seems that Bugzilla (https://bugs.llvm.org/) is down, when I using the search engine. -- Best Regards, Xing

Is "Unix Makefiles" what I want if I am building on Windows using GNU make? At 7/28/2020 10:41 PM, Xing GUO wrote: >On 7/29/20, Paul C. Anagnostopoulos via llvm-dev ><llvm-dev at lists.llvm.org> wrote: >> Folks, >> >> Total newbie here. What is the simplest way to build a single .rst file so >> that I can look at the generated HTML? I have CMake,

Hi folks, Several days ago, I made a bad change in llvm, and I reverted it using following command ``` $ svn merge -r <bad change revision>:<previous revision> ``` However, this command seemed not working properly. I would like to know, what's the right way to revert a bad change. I notice that there are some reverting change with proper message, e.g. "Revert: [some tag]

Folks, Total newbie here. What is the simplest way to build a single .rst file so that I can look at the generated HTML? I have CMake, Python, and Sphinx installed. ~~ Paul

Hi, I am very excited to take the awesome tutorial of implementing *Kaleidoscope*. But I got stuck here... I have done the AST parsing, however, when I introduce these 'llvm/IR/*' headers, I got a compiling error... But if I delete these headers it runs well ... """headers #include "llvm/IR/BasicBlock.h" #include "llvm/IR/Constants.h" #include

Hi folks, It seems that bugzilla is encountering some problems right now. When I click specific bug reports, it shows "undef error - DBD::mysql::st execute failed: Got error 28 from storage engine", e.g. https://bugs.llvm.org/show_bug.cgi?id=41513 and https://bugs.llvm.org/show_bug.cgi?id=46423 -- Cheers, Xing

Dear LLVM Team: My name is Guo Xing, a student who are in his third year of college. GSoC2018 is coming, and I want to do some contribution for llvm community. However, the open projects page is for GSoC2017, and some projects like Shell auto-completion support for clang <http://llvm.org/OpenProjects.html#clang-shell-autocompletion-support> have been done. Is there any ideas? What if

It seems to be down again for me, anyone experiencing the same? https://bugs.llvm.org/show_bug.cgi?id=18159 On Tue, 23 Jun 2020 at 14:54, Aaron Ballman via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Tue, Jun 23, 2020 at 8:28 AM Xing GUO via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > > > Hi folks, > > > > It seems that bugzilla is

On 5/21/20, Adrian Prantl <aprantl at apple.com> wrote: > I think the example looks like it would be really useful for many categories > of testcases! > Will it still be possible to manually specify the .debug_abbrev section when > this is desired after you are done? Yes, I think it works. There are two ways to edit the .debug_abbrev section. i) Edit the "Attr:" and

Hi, everyone ! I want to upload a patch after creating a bug-41763, https://bugs.llvm.org/show_bug.cgi?id=41763 How to upload a patch? Is there a user-manual ? Thanks ~ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190506/4c1fa793/attachment.html>

Hi Pavel, Thanks for your comments! On 5/21/20, Pavel Labath <pavel at labath.sk> wrote: > Hello Xing, > > I think the proposal looks very useful. I think it will be fairly tricky > to get all of the details right though. There is a lot of "inferring" > going on there, and getting that to work reliably and with predictable > results will need careful

Madhur Amilkanthwar via llvm-dev <llvm-dev at lists.llvm.org>於 2020年8月9日 週日，上午1:53寫道： > Hi Paul, > I hope you have gone through > https://llvm.org/docs/Contributing.html#how-to-submit-a-patch. > > Generally, I would do 'git add' on the new file. 'git diff' should show me > the newly added file. Further, I'd just do 'arc diff' and this should

net dmz:192.168.0.1 tcp 80 I forgot to mention that this should be put to rules file, sorry. _____ Von: Michael Weickel - iQom Business Services GmbH [mailto:mw@iqom.de] Gesendet: Dienstag, 2. Februar 2010 17:37 An: ''Shorewall Users'' Betreff: AW: [Shorewall-users] Suddenly DMZ can''t access to internet No. For

On Thu, Jan 21, 2016 at 7:04 PM, Brian Cain via cfe-dev < cfe-dev at lists.llvm.org> wrote: > SuSE Linux Enterprise Server 11SP3 x86_64 > > Looks like I see several failures that weren't in 3.7.1. Is there any way > to tell whether these are regressions vs new-to-3.8.0-but-failing? The > MSan ones were in 3.7.1 but the ThreadPoolTest and the libc++ errors were > not

Hi everyone, I'm looking through codes related to registered pressure tracking, mainly the source files 'RegisterPressure.h/cpp', 'MachineRegisterInfo.h/cpp', 'TargetRegisterInfo.h/cpp'. There is a concept I can hardly understand, the 'register pressure set'. Class 'TargetRegisterInfo' defines two virtual methods 'getRegClassPressureSets' and

Personally I'd like a "git llvm fetch-diff D1234" subcommand, which outputs a patch in the format of "git format-patch", which, you could then pipe to "git am", say, providing whatever prefix options you like. On Fri, Feb 8, 2019 at 2:41 PM Mehdi AMINI via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > Are you trying to apply a revision

Fellow Rail users and developers, Right now the easiest way to run Rails is in combination with Mongrel. However, it may not be a good idea to expose Mongrel directly to the outside world in a high-load production environment. In-addition, Mongrel_cluster + proxy + load balancer have to be used even for a single server deployment making the unified setup more complicated than needs be.

Hi LLVM community, Currently LLVM backend do pre-RA machine instruction scheduling in non-SSA form, I doubt why not do machine scheduling in SSA machine instruction form? Now LLVM’s machine scheduling uses a list-scheduling algorithm, but if we wang to support more complex scheduling algorithms, for example, modulo scheduling for loops, it seems more easy to accomplish this in SSA form as SSA is