[PATCH] [compiler-rt] _udivdi3(), _umoddi3(), _moddi3() and _divdi3() routines not properly "tuned"

[Stefan Kanthak via llvm-commits]

Eli Friedman <efriedma at codeaurora.org> wrote:

> Please see 
> http://llvm.org/docs/DeveloperPolicy.html#making-and-submitting-a-patch 
> for directions to submit a patch.

A)

>From <http://llvm.org/docs/DeveloperPolicy.html#developer-policies>:

| This section contains policies that pertain to frequent LLVM
| developers. We always welcome one-off patches from people who
| do not routinely contribute to LLVM, but we expect more from
| frequent contributors to keep the system as efficient as possible
| for everyone. Frequent LLVM contributors are expected to meet the
| following requirements in order for LLVM to maintain a high standard
| of quality.

Do I qualify as frequent LLVM developer?

B)

The primary target for my bug report was <llvm-bugs at lists.llvm.org>;
LLVM is but apparently not interested in bug reports (I consider not
properly tuned code, which is but attributed as "tuned", buggy), so
they bounce mails to this list for non-subscribers.
As I don't use LLVM I have absolutely no interest to subscribe there.

JFTR: the LLVM website doesn't list a mail address for vulnerability
      reports (or at least I haven't found it).

C)

| If you use a different tool, make sure it uses the diff -u format
| and that it doesn't contain clutter which makes it hard to read.

Please tell my how to invoke "diff" on Windows.

JFTR: LLVM-6.0.0-r316086-win32.exe contains no "diff".

I have (the bare mininum of) several Windows SDKs and their
toolchains installed here, for use on the command line; no fancy
bloatware like Visual Studio, just the compiler, assembler, linker,
and [n]make.
I can offer the output of "FC.exe /N" or "WINDIFF.exe".-P

JFTR: the market share of Windows is about 10 times that of systems
      which come with a "diff" preinstalled.

> General mailing list etiquette: If you're going to reply to an existing 
> thread, please use the "reply" button in your mail client so it's 
> threaded properly (even if you're replying to yourself). (Original 
> message: 
> http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20171106/500748.html 
> )

VERY FUNNY!
Where does this "original" show the MID that a MUA needs to include
in the reply?

regards
Stefan

[ braindead fullquote removed ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: i386_di3.diff
Type: application/octet-stream
Size: 26572 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20171110/9fc17b76/attachment.obj>