similar to: Clang is a resource hog, the installers for Windows miss quite some files, and are defect!

"Michael Kruse" <llvmdev at meinersbur.de> wrote: > I think David is not referring to the capitalization of file names, but to > "DUPLICATE", "WASTING", "NOT AMUSED", "BOGUS" etc. I EMPHASIZE in the only way possible with plain text. > It should be possible to report problems in a professional manner. It should also be possible

Hi, I am using a railsapp to call an external app and print some barcode-labels. My problem is, after a while there seems to be a timeout. Then I need to stop the Mongrel-Server and restart it. Below you can see the error message, when i stop the server. Has somebody seen this before? Greetings, Oli C:\etikett>mongrel_rails start -d -e production ** WARNING: Win32 does not support daemon

Hi Stefan, You can find the contribution guidelines here : https://llvm.org/docs/Contributing.html LLVM also have code of conduct : https://llvm.org/docs/CodeOfConduct.html On Sun, 23 Aug 2020 at 23:28, David Blaikie via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > On Sun, Aug 23, 2020 at 10:54 AM Stefan Kanthak <stefan.kanthak at nexgo.de> > wrote: > >>

"David Blaikie" <dblaikie at gmail.com> wrote: > Context is everything. I'm willing to accept your humble apologies. > Spotting the relevant details in long build output > can be tricky & some emphasis (caps, the *** borders, etc) can be useful. So you dare to "shout" at your users/customers, but mock when someone (me) uses the same sort of emphasis,

Who's "shouting" here? Even in complete lines, 9 consecutive words! PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: clang: note: diagnostic msg: C:\Windows\Temp\crash-74a40f.c clang: note: diagnostic msg: C:\Windows\Temp\crash-74a40f.sh clang: note: diagnostic msg: ******************** --- crash-74a40f.c ---

Hallo, I try to boot the windows 98 bootdisk via memdisk. It doesn't work completely. Booting a freedos FD image works, booting the windows 98 image works too. But the windows 98 boot disk then should extract the file "ebd.cab" with the file "extract.com", and that step fails. Is that a syslinux problem or a windows problem? Viele Gruesse! Helmut

"Philip Reames" <listmail at philipreames.com> wrote: > Stefan, > > I can't tell if you're intentionally trolling, or are simply oblivious, > but to this observer you have clearly crossed well over the line of > acceptable behavior. Since you seem to have some experience in taking the point of view of a third person: do you find LLVM's

"David Greene" <dag at hpe.com> wrote: > Stefan Kanthak via llvm-dev <llvm-dev at lists.llvm.org> writes: > >> "Michael Kruse" <llvmdev at meinersbur.de> wrote: >> >>> I think David is not referring to the capitalization of file names, but to >>> "DUPLICATE", "WASTING", "NOT AMUSED",

"Eric Christopher" <echristo at gmail.com> wrote: [...] > Please take that step back that Philip requested. Please take that step back that I requested (also on behalf of at least one of your prospect customers/users). > We do appreciate the bug reports, but not the delivery. We do appreciate your work, but not its (current) delivery! > Thanks and have a good

On Tue, Dec 4, 2018 at 3:58 PM Daniel Sanders via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Dec 4, 2018, at 15:11, Stefan Kanthak <stefan.kanthak at nexgo.de> wrote: > No, I understand his intent. I just doesn't align with my intent, > including the hoops he/LLVM wants me to jump through. > > He's not saying they're your bugs, he's just saying

Hi there, I have seen in the file column plugin ( http://www.kanthak.net/opensource/file_column/) from Sebastian Kanthak or David''s acts_as_taggable plugin that to register my functionality I need to do something like this: ApplicationHelper.send(:include, InPlaceEditAssociations) I am wondering why not: (a) module ApplicationHelper include InPlaceEditAssociatons end or: (b)

"Tim Northover" <t.p.northover at gmail.com> wrote: > Hi, > > On Sat, 1 Dec 2018 at 17:37, Stefan Kanthak via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Compile the following functions with "-O3 -target amd64" > > You've been advised before, but you really need to start reporting > these as bugs[*] if you actually care about

Hello, When running test-release.sh using GCC 5.4.0 we encountered this error : /home/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/clang-tools-extra/clangd/Hover.cpp: In function ‘llvm::StringLiteral clang::clangd::{anonymous}::getNameForExpr(const clang::Expr*)’: /home/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/clang-tools-extra/clangd/Hover.cpp:450:10: error: could not convert

"H. Peter Anvin" <hpa at zytor.com> wrote August 20, 2019 12:51 AM: > On 8/14/19 9:42 PM, Stefan Kanthak wrote: >> Hi, >> >> both >> https://git.kernel.org/pub/scm/libs/klibc/klibc.git/plain/usr/klibc/arch/i386/libgcc/__ashldi3.S >> and >> https://git.kernel.org/pub/scm/libs/klibc/klibc.git/plain/usr/klibc/arch/i386/libgcc/__lshrdi3.S

I am pleased to announce that LLVM 10 is now available. Get it here: https://llvm.org/releases/download.html#10.0.0 This release is the result of the LLVM community's work over the past six months (up to to e26a78e7085 on master plus commits up to d32170dbd5b on the release/10.x branch). Some highlights include: - C++ Concepts support in Clang - Clang no longer runs in a separate process

I am pleased to announce that LLVM 10 is now available. Get it here: https://llvm.org/releases/download.html#10.0.0 This release is the result of the LLVM community's work over the past six months (up to to e26a78e7085 on master plus commits up to d32170dbd5b on the release/10.x branch). Some highlights include: - C++ Concepts support in Clang - Clang no longer runs in a separate process

Hello everyone, It took a bit longer than planned due to master being a somewhat unstable at the branch point, but Release Candidate 1 has now been tagged as llvmorg-10.0.0-rc1. Source code and docs are available at https://prereleases.llvm.org/10.0.0/#rc1 Pre-built binaries will be added there as they become available. Please file bug reports for any issues you find as blockers of

Hello everyone, Release Candidate 4 was tagged earlier today as llvmorg-10.0.0-rc4 on the release branch at b406eab8880. It contains 12 commits since the previous release candidate. If no new problems arise, this is what the final release will look like. Source code and docs are available at https://prereleases.llvm.org/10.0.0/#rc4 and

Hello everyone, Release Candidate 2 was tagged earlier today as llvmorg-10.0.0-rc2. It includes 98 commits since the previous release candidate. Source code and docs are available at https://prereleases.llvm.org/10.0.0/#rc2 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc2 Pre-built binaries will be added as they become available. Please file bug reports for any issues

Hello everyone, It took a bit longer than planned, but Release Candidate 3 is now here. It was tagged as llvmorg-10.0.0-rc3 on the release branch at 3a843031a5 and contains 95 commits since the previous release candidate. If no new problems arise, this is what the final release will look like. Source code and docs are available at https://prereleases.llvm.org/10.0.0/#rc3 and