thr3ads.net - llvm dev - [llvm-dev] Apropos "shouting": PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT [Aug 2020]

If this information is useful, please help other people find it:
Share via:

Praveen Velliengiri via llvm-dev

2020-Aug-23 18:03 UTC

[llvm-dev] Apropos "shouting": PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT

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.
>>
>
> Sarcasm and snark are not appreciated. Your repeated interest in
> antagonizing communication is not suited to this community.
>
>
>> > 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, albeit just on SINGLE words, not whole
>> lines?
>> "o tempora, o mores!"
>>
>> Alternative, NOT "shouting":
>> ____________________________________________________
>> Please attach the following files to the bug report:
>> ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
>> Hint: even the Windows console allows to output INVERSE text, which
>>       would be even more outstanding and easier to spot.
>>
>> Also: starred **** borders are not as outstanding as hashed #### or
>>       slashed //// borders!
>>
>> Now go and fix the bug resulting in the crash I demonstrated below!
>>
>> Stefan
>>
>> > On Sun, Aug 23, 2020 at 5:21 AM Stefan Kanthak via llvm-dev <
>> > llvm-dev at lists.llvm.org> wrote:
>> >
>> >> 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 ---
>> >> # 1 "<built-in>"
>> >> # 1 "crash.c"
>> >> // Copyright (C) 2020 Stefan Kanthak <stefan.kanthak at
nexgo.de>
>> >>
>> >> long dummy;
>> >>
>> >> __attribute__((naked))
>> >> long function(void)
>> >> {
>> >>    __asm__(".data\n"
>> >>            "dummy:\n"
>> >>            ".quad\t0\n"
>> >>            ".text\n"
>> >>            ".intel_syntax noprefix\n"
>> >>            "\tmov\trax, dummy\n"
>> >>            "\tret\n");
>> >> }
>> >> --- EOF ---
>> >>
>> >> --- crash-74a40f.sh ---
>> >> # Crash reproducer for clang version 10.0.0
>> >> # Driver args: "-c" "-m64"
"crash.c"
>> >> # Original command:  "C:\\Program
Files\\LLVM\\bin\\clang.exe" "-cc1"
>> >> "-triple"
>> >> "x86_64-pc-windows-msvc19.11.0"
"-emit-obj" "-mrelax-all"
>> >> "-mincremental-linker-
>> >> compatible" "-disable-free"
"-disable-llvm-verifier"
>> >> "-discard-value-names" "-ma
>> >> in-file-name" "crash.c"
"-mrelocation-model" "pic" "-pic-level"
"2"
>> >> "-mthread-mo
>> >> del" "posix" "-mframe-pointer=none"
"-fmath-errno" "-fno-rounding-math"
>> >> "-masm-v
>> >> erbose" "-mconstructor-aliases"
"-munwind-tables" "-target-cpu"
>> "x86-64"
>> >> "-dwarf
>> >> -column-info" "-resource-dir" "C:\\Program
>> >> Files\\LLVM\\lib\\clang\\10.0.0" "-in
>> >> ternal-isystem" "C:\\Program
Files\\LLVM\\lib\\clang\\10.0.0\\include"
>> >> "-fdebug-
>> >> compilation-dir" "C:\\Windows\\Temp"
"-ferror-limit" "19"
>> >> "-fmessage-length" "80
>> >> " "-fno-use-cxa-atexit"
"-fms-extensions" "-fms-compatibility"
>> >> "-fms-compatibili
>> >> ty-version=19.11" "-fdelayed-template-parsing"
"-fobjc-runtime=gcc"
>> >> "-fdiagnosti
>> >> cs-show-option" "-fcolor-diagnostics"
"-faddrsig" "-o" "crash.o" "-x"
>> "c"
>> >> "crash
>> >> .c"
>> >>  "C:\\Program Files\\LLVM\\bin\\clang.exe"
"-cc1" "-triple"
>> >> "x86_64-pc-windows-m
>> >> svc19.11.0" "-emit-obj" "-mrelax-all"
"-mincremental-linker-compatible"
>> >> "-disabl
>> >> e-free" "-disable-llvm-verifier"
"-discard-value-names"
>> "-main-file-name"
>> >> "crash
>> >> .c" "-mrelocation-model" "pic"
"-pic-level" "2" "-mthread-model"
>> "posix"
>> >> "-mfram
>> >> e-pointer=none" "-fmath-errno"
"-fno-rounding-math" "-masm-verbose"
>> >> "-mconstruct
>> >> or-aliases" "-munwind-tables"
"-target-cpu" "x86-64"
>> "-dwarf-column-info"
>> >> "-ferr
>> >> or-limit" "19" "-fmessage-length"
"80" "-fno-use-cxa-atexit"
>> >> "-fms-extensions" "
>> >> -fms-compatibility"
"-fms-compatibility-version=19.11"
>> >> "-fdelayed-template-parsi
>> >> ng" "-fobjc-runtime=gcc"
"-fdiagnostics-show-option"
>> "-fcolor-diagnostics"
>> >> "-fad
>> >> drsig" "-x" "c"
"crash-74a40f.c"
>> >> --- EOF ---
>> >>
>> >> fatal error: error in backend: symbol 'dummy' is
already defined
>> >> Stack dump:
>> >> 0.      Program arguments: C:\Program Files\LLVM\bin\clang.exe
-c -m64
>> >> crash.c
>> >> 1.      <eof> parser at end of file
>> >> 2.      Code generation
>> >>  #0 0x000007fefd2eb87d
(C:\Windows\system32\KERNELBASE.dll+0xb87d)
>> >>  #1 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x16b6eca
>> >> C:\Program Files\LLVM\bin\clang.exe 0x16935a3
>> >>  #2 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x71f9
>> >> C:\Program Files\LLVM\bin\clang.exe 0x16bbee7
>> >>  #3 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x1f84176
>> >> C:\Program Files\LLVM\bin\clang.exe 0x1f892b7
>> >>  #4 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x1198ec1
>> >> C:\Program Files\LLVM\bin\clang.exe 0x1199442
>> >>  #5 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x18e1cb3
>> >> C:\Program Files\LLVM\bin\clang.exe 0x36ab935
>> >>  #6 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x28898a3
>> >> C:\Program Files\LLVM\bin\clang.exe 0x1dadb02
>> >>  #7 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x1d70bc0
>> >> C:\Program Files\LLVM\bin\clang.exe 0x1e08ca9
>> >>  #8 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x6ebf
>> >> C:\Program Files\LLVM\bin\clang.exe 0x4337
>> >>  #9 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x1d0d7c6
>> >> C:\Program Files\LLVM\bin\clang.exe 0x16b6d33
>> >> #10 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x1d0d00b
>> >> C:\Program Files\LLVM\bin\clang.exe 0x1c311d8
>> >> #11 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x1c316d4
>> >> C:\Program Files\LLVM\bin\clang.exe 0x1c1f357
>> >> #12 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x3c93
>> >> C:\Program Files\LLVM\bin\clang.exe 0x36c74a0
>> >> #13 0x0000000140db6eca (C:\Program
Files\LLVM\bin\clang.exe+0x16b6eca)
>> >> #14 0x0000000140d935a3 (C:\Program
Files\LLVM\bin\clang.exe+0x16935a3)
>> >> [...]
>> >> clang: error: clang frontend command failed with exit code 70
(use -v
>> to
>> >> see invocation)
>> >> clang version 10.0.0
>> >> Target: x86_64-pc-windows-msvc
>> >> Thread model: posix
>> >> InstalledDir: C:\Program Files\LLVM\bin
>> >> clang: note: diagnostic msg: PLEASE submit a bug report to
>> >> https://bugs.llvm.org/ and include the crash backtrace,
preprocessed
>> >> source, and associated run script.
>> >> clang: note: diagnostic msg:
>> >> ********************
>> >> _______________________________________________
>> >> LLVM Developers mailing list
>> >> llvm-dev at lists.llvm.org
>> >> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>> >>
>>
>> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200823/866cfe9c/attachment.html>

Stefan Kanthak via llvm-dev

2020-Aug-23 18:41 UTC

head link

[llvm-dev] Apropos "shouting": PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT

"Praveen Velliengiri" <praveenvelliengiri at gmail.com> wrote:
> 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
Does your code of conduct allow you to waste your users resources?
Mine doesn't!
Or to mock about my way of emphasizing by writing SINGLE words in upper
case, while your "product" uses whole lines/sentences in upper case?

"quod licet jovi non licet bovi"?

Stefan

PS: I prefer fast and bug-free code over some code of conduct!

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.
>>
>
> Sarcasm and snark are not appreciated. Your repeated interest in
> antagonizing communication is not suited to this community.
>
>
>> > 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, albeit just on SINGLE words, not whole
>> lines?
>> "o tempora, o mores!"
>>
>> Alternative, NOT "shouting":
>> ____________________________________________________
>> Please attach the following files to the bug report:
>> ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
>> Hint: even the Windows console allows to output INVERSE text, which
>>       would be even more outstanding and easier to spot.
>>
>> Also: starred **** borders are not as outstanding as hashed #### or
>>       slashed //// borders!
>>
>> Now go and fix the bug resulting in the crash I demonstrated below!
>>
>> Stefan
>>
>> > On Sun, Aug 23, 2020 at 5:21 AM Stefan Kanthak via llvm-dev <
>> > llvm-dev at lists.llvm.org> wrote:
>> >
>> >> 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 ---
>> >> # 1 "<built-in>"
>> >> # 1 "crash.c"
>> >> // Copyright (C) 2020 Stefan Kanthak <stefan.kanthak at
nexgo.de>
>> >>
>> >> long dummy;
>> >>
>> >> __attribute__((naked))
>> >> long function(void)
>> >> {
>> >>    __asm__(".data\n"
>> >>            "dummy:\n"
>> >>            ".quad\t0\n"
>> >>            ".text\n"
>> >>            ".intel_syntax noprefix\n"
>> >>            "\tmov\trax, dummy\n"
>> >>            "\tret\n");
>> >> }
>> >> --- EOF ---
>> >>
>> >> --- crash-74a40f.sh ---
>> >> # Crash reproducer for clang version 10.0.0
>> >> # Driver args: "-c" "-m64"
"crash.c"
>> >> # Original command:  "C:\\Program
Files\\LLVM\\bin\\clang.exe" "-cc1"
>> >> "-triple"
>> >> "x86_64-pc-windows-msvc19.11.0"
"-emit-obj" "-mrelax-all"
>> >> "-mincremental-linker-
>> >> compatible" "-disable-free"
"-disable-llvm-verifier"
>> >> "-discard-value-names" "-ma
>> >> in-file-name" "crash.c"
"-mrelocation-model" "pic" "-pic-level"
"2"
>> >> "-mthread-mo
>> >> del" "posix" "-mframe-pointer=none"
"-fmath-errno" "-fno-rounding-math"
>> >> "-masm-v
>> >> erbose" "-mconstructor-aliases"
"-munwind-tables" "-target-cpu"
>> "x86-64"
>> >> "-dwarf
>> >> -column-info" "-resource-dir" "C:\\Program
>> >> Files\\LLVM\\lib\\clang\\10.0.0" "-in
>> >> ternal-isystem" "C:\\Program
Files\\LLVM\\lib\\clang\\10.0.0\\include"
>> >> "-fdebug-
>> >> compilation-dir" "C:\\Windows\\Temp"
"-ferror-limit" "19"
>> >> "-fmessage-length" "80
>> >> " "-fno-use-cxa-atexit"
"-fms-extensions" "-fms-compatibility"
>> >> "-fms-compatibili
>> >> ty-version=19.11" "-fdelayed-template-parsing"
"-fobjc-runtime=gcc"
>> >> "-fdiagnosti
>> >> cs-show-option" "-fcolor-diagnostics"
"-faddrsig" "-o" "crash.o" "-x"
>> "c"
>> >> "crash
>> >> .c"
>> >>  "C:\\Program Files\\LLVM\\bin\\clang.exe"
"-cc1" "-triple"
>> >> "x86_64-pc-windows-m
>> >> svc19.11.0" "-emit-obj" "-mrelax-all"
"-mincremental-linker-compatible"
>> >> "-disabl
>> >> e-free" "-disable-llvm-verifier"
"-discard-value-names"
>> "-main-file-name"
>> >> "crash
>> >> .c" "-mrelocation-model" "pic"
"-pic-level" "2" "-mthread-model"
>> "posix"
>> >> "-mfram
>> >> e-pointer=none" "-fmath-errno"
"-fno-rounding-math" "-masm-verbose"
>> >> "-mconstruct
>> >> or-aliases" "-munwind-tables"
"-target-cpu" "x86-64"
>> "-dwarf-column-info"
>> >> "-ferr
>> >> or-limit" "19" "-fmessage-length"
"80" "-fno-use-cxa-atexit"
>> >> "-fms-extensions" "
>> >> -fms-compatibility"
"-fms-compatibility-version=19.11"
>> >> "-fdelayed-template-parsi
>> >> ng" "-fobjc-runtime=gcc"
"-fdiagnostics-show-option"
>> "-fcolor-diagnostics"
>> >> "-fad
>> >> drsig" "-x" "c"
"crash-74a40f.c"
>> >> --- EOF ---
>> >>
>> >> fatal error: error in backend: symbol 'dummy' is
already defined
>> >> Stack dump:
>> >> 0.      Program arguments: C:\Program Files\LLVM\bin\clang.exe
-c -m64
>> >> crash.c
>> >> 1.      <eof> parser at end of file
>> >> 2.      Code generation
>> >>  #0 0x000007fefd2eb87d
(C:\Windows\system32\KERNELBASE.dll+0xb87d)
>> >>  #1 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x16b6eca
>> >> C:\Program Files\LLVM\bin\clang.exe 0x16935a3
>> >>  #2 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x71f9
>> >> C:\Program Files\LLVM\bin\clang.exe 0x16bbee7
>> >>  #3 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x1f84176
>> >> C:\Program Files\LLVM\bin\clang.exe 0x1f892b7
>> >>  #4 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x1198ec1
>> >> C:\Program Files\LLVM\bin\clang.exe 0x1199442
>> >>  #5 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x18e1cb3
>> >> C:\Program Files\LLVM\bin\clang.exe 0x36ab935
>> >>  #6 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x28898a3
>> >> C:\Program Files\LLVM\bin\clang.exe 0x1dadb02
>> >>  #7 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x1d70bc0
>> >> C:\Program Files\LLVM\bin\clang.exe 0x1e08ca9
>> >>  #8 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x6ebf
>> >> C:\Program Files\LLVM\bin\clang.exe 0x4337
>> >>  #9 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x1d0d7c6
>> >> C:\Program Files\LLVM\bin\clang.exe 0x16b6d33
>> >> #10 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x1d0d00b
>> >> C:\Program Files\LLVM\bin\clang.exe 0x1c311d8
>> >> #11 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x1c316d4
>> >> C:\Program Files\LLVM\bin\clang.exe 0x1c1f357
>> >> #12 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x3c93
>> >> C:\Program Files\LLVM\bin\clang.exe 0x36c74a0
>> >> #13 0x0000000140db6eca (C:\Program
Files\LLVM\bin\clang.exe+0x16b6eca)
>> >> #14 0x0000000140d935a3 (C:\Program
Files\LLVM\bin\clang.exe+0x16935a3)
>> >> [...]
>> >> clang: error: clang frontend command failed with exit code 70
(use -v
>> to
>> >> see invocation)
>> >> clang version 10.0.0
>> >> Target: x86_64-pc-windows-msvc
>> >> Thread model: posix
>> >> InstalledDir: C:\Program Files\LLVM\bin
>> >> clang: note: diagnostic msg: PLEASE submit a bug report to
>> >> https://bugs.llvm.org/ and include the crash backtrace,
preprocessed
>> >> source, and associated run script.
>> >> clang: note: diagnostic msg:
>> >> ********************

Tanya Lattner via llvm-dev

2020-Aug-23 19:11 UTC

head link

[llvm-dev] Apropos "shouting": PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT

Stefan,

There have been several requests from community members to respect our code of
conduct. I’ll send you an email offline so we discuss further.

Thanks,
Tanya
> On Aug 23, 2020, at 11:41 AM, Stefan Kanthak via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> "Praveen Velliengiri" <praveenvelliengiri at gmail.com>
wrote:
> 
>> 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
> 
> Does your code of conduct allow you to waste your users resources?
> Mine doesn't!
> Or to mock about my way of emphasizing by writing SINGLE words in upper
> case, while your "product" uses whole lines/sentences in upper
case?
> 
> "quod licet jovi non licet bovi"?
> 
> Stefan
> 
> PS: I prefer fast and bug-free code over some code of conduct!
> 
> 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.
>>> 
>> 
>> Sarcasm and snark are not appreciated. Your repeated interest in
>> antagonizing communication is not suited to this community.
>> 
>> 
>>>> 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, albeit just on SINGLE words, not
whole
>>> lines?
>>> "o tempora, o mores!"
>>> 
>>> Alternative, NOT "shouting":
>>> ____________________________________________________
>>> Please attach the following files to the bug report:
>>> ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
>>> Hint: even the Windows console allows to output INVERSE text, which
>>>      would be even more outstanding and easier to spot.
>>> 
>>> Also: starred **** borders are not as outstanding as hashed #### or
>>>      slashed //// borders!
>>> 
>>> Now go and fix the bug resulting in the crash I demonstrated below!
>>> 
>>> Stefan
>>> 
>>>> On Sun, Aug 23, 2020 at 5:21 AM Stefan Kanthak via llvm-dev
<
>>>> llvm-dev at lists.llvm.org> wrote:
>>>> 
>>>>> 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 ---
>>>>> # 1 "<built-in>"
>>>>> # 1 "crash.c"
>>>>> // Copyright (C) 2020 Stefan Kanthak <stefan.kanthak at
nexgo.de>
>>>>> 
>>>>> long dummy;
>>>>> 
>>>>> __attribute__((naked))
>>>>> long function(void)
>>>>> {
>>>>>   __asm__(".data\n"
>>>>>           "dummy:\n"
>>>>>           ".quad\t0\n"
>>>>>           ".text\n"
>>>>>           ".intel_syntax noprefix\n"
>>>>>           "\tmov\trax, dummy\n"
>>>>>           "\tret\n");
>>>>> }
>>>>> --- EOF ---
>>>>> 
>>>>> --- crash-74a40f.sh ---
>>>>> # Crash reproducer for clang version 10.0.0
>>>>> # Driver args: "-c" "-m64"
"crash.c"
>>>>> # Original command:  "C:\\Program
Files\\LLVM\\bin\\clang.exe" "-cc1"
>>>>> "-triple"
>>>>> "x86_64-pc-windows-msvc19.11.0"
"-emit-obj" "-mrelax-all"
>>>>> "-mincremental-linker-
>>>>> compatible" "-disable-free"
"-disable-llvm-verifier"
>>>>> "-discard-value-names" "-ma
>>>>> in-file-name" "crash.c"
"-mrelocation-model" "pic" "-pic-level"
"2"
>>>>> "-mthread-mo
>>>>> del" "posix"
"-mframe-pointer=none" "-fmath-errno"
"-fno-rounding-math"
>>>>> "-masm-v
>>>>> erbose" "-mconstructor-aliases"
"-munwind-tables" "-target-cpu"
>>> "x86-64"
>>>>> "-dwarf
>>>>> -column-info" "-resource-dir"
"C:\\Program
>>>>> Files\\LLVM\\lib\\clang\\10.0.0" "-in
>>>>> ternal-isystem" "C:\\Program
Files\\LLVM\\lib\\clang\\10.0.0\\include"
>>>>> "-fdebug-
>>>>> compilation-dir" "C:\\Windows\\Temp"
"-ferror-limit" "19"
>>>>> "-fmessage-length" "80
>>>>> " "-fno-use-cxa-atexit"
"-fms-extensions" "-fms-compatibility"
>>>>> "-fms-compatibili
>>>>> ty-version=19.11"
"-fdelayed-template-parsing" "-fobjc-runtime=gcc"
>>>>> "-fdiagnosti
>>>>> cs-show-option" "-fcolor-diagnostics"
"-faddrsig" "-o" "crash.o" "-x"
>>> "c"
>>>>> "crash
>>>>> .c"
>>>>> "C:\\Program Files\\LLVM\\bin\\clang.exe"
"-cc1" "-triple"
>>>>> "x86_64-pc-windows-m
>>>>> svc19.11.0" "-emit-obj"
"-mrelax-all" "-mincremental-linker-compatible"
>>>>> "-disabl
>>>>> e-free" "-disable-llvm-verifier"
"-discard-value-names"
>>> "-main-file-name"
>>>>> "crash
>>>>> .c" "-mrelocation-model" "pic"
"-pic-level" "2" "-mthread-model"
>>> "posix"
>>>>> "-mfram
>>>>> e-pointer=none" "-fmath-errno"
"-fno-rounding-math" "-masm-verbose"
>>>>> "-mconstruct
>>>>> or-aliases" "-munwind-tables"
"-target-cpu" "x86-64"
>>> "-dwarf-column-info"
>>>>> "-ferr
>>>>> or-limit" "19" "-fmessage-length"
"80" "-fno-use-cxa-atexit"
>>>>> "-fms-extensions" "
>>>>> -fms-compatibility"
"-fms-compatibility-version=19.11"
>>>>> "-fdelayed-template-parsi
>>>>> ng" "-fobjc-runtime=gcc"
"-fdiagnostics-show-option"
>>> "-fcolor-diagnostics"
>>>>> "-fad
>>>>> drsig" "-x" "c"
"crash-74a40f.c"
>>>>> --- EOF ---
>>>>> 
>>>>> fatal error: error in backend: symbol 'dummy' is
already defined
>>>>> Stack dump:
>>>>> 0.      Program arguments: C:\Program
Files\LLVM\bin\clang.exe -c -m64
>>>>> crash.c
>>>>> 1.      <eof> parser at end of file
>>>>> 2.      Code generation
>>>>> #0 0x000007fefd2eb87d
(C:\Windows\system32\KERNELBASE.dll+0xb87d)
>>>>> #1 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x16b6eca
>>>>> C:\Program Files\LLVM\bin\clang.exe 0x16935a3
>>>>> #2 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x71f9
>>>>> C:\Program Files\LLVM\bin\clang.exe 0x16bbee7
>>>>> #3 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x1f84176
>>>>> C:\Program Files\LLVM\bin\clang.exe 0x1f892b7
>>>>> #4 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x1198ec1
>>>>> C:\Program Files\LLVM\bin\clang.exe 0x1199442
>>>>> #5 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x18e1cb3
>>>>> C:\Program Files\LLVM\bin\clang.exe 0x36ab935
>>>>> #6 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x28898a3
>>>>> C:\Program Files\LLVM\bin\clang.exe 0x1dadb02
>>>>> #7 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x1d70bc0
>>>>> C:\Program Files\LLVM\bin\clang.exe 0x1e08ca9
>>>>> #8 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x6ebf
>>>>> C:\Program Files\LLVM\bin\clang.exe 0x4337
>>>>> #9 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x1d0d7c6
>>>>> C:\Program Files\LLVM\bin\clang.exe 0x16b6d33
>>>>> #10 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x1d0d00b
>>>>> C:\Program Files\LLVM\bin\clang.exe 0x1c311d8
>>>>> #11 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x1c316d4
>>>>> C:\Program Files\LLVM\bin\clang.exe 0x1c1f357
>>>>> #12 0x0000000140db6eca C:\Program Files\LLVM\bin\clang.exe
0x3c93
>>>>> C:\Program Files\LLVM\bin\clang.exe 0x36c74a0
>>>>> #13 0x0000000140db6eca (C:\Program
Files\LLVM\bin\clang.exe+0x16b6eca)
>>>>> #14 0x0000000140d935a3 (C:\Program
Files\LLVM\bin\clang.exe+0x16935a3)
>>>>> [...]
>>>>> clang: error: clang frontend command failed with exit code
70 (use -v
>>> to
>>>>> see invocation)
>>>>> clang version 10.0.0
>>>>> Target: x86_64-pc-windows-msvc
>>>>> Thread model: posix
>>>>> InstalledDir: C:\Program Files\LLVM\bin
>>>>> clang: note: diagnostic msg: PLEASE submit a bug report to
>>>>> https://bugs.llvm.org/ and include the crash backtrace,
preprocessed
>>>>> source, and associated run script.
>>>>> clang: note: diagnostic msg:
>>>>> ********************
> 
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

llvm dev - Aug 2020 - Apropos "shouting": PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT

[llvm-dev] Apropos "shouting": PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT

[llvm-dev] Apropos "shouting": PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT

[llvm-dev] Apropos "shouting": PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT