* [ISSUE] Chromium CFI
@ 2021-10-15 20:37 anon-lestat
2021-10-15 22:19 ` q66
` (7 more replies)
0 siblings, 8 replies; 9+ messages in thread
From: anon-lestat @ 2021-10-15 20:37 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 527 bytes --]
New issue by anon-lestat on void-packages repository
https://github.com/void-linux/void-packages/issues/33579
Description:
Chromium on void linux has broken CFI with LLVM 12.0.1.
As illustrated by its template starting with line 225:
# segfaults with llvm-12.0.1
'is_cfi=false'
'use_thin_lto=false'
'use_cfi_icall=false'
'chrome_pgo_phase=0'
Even if it cant be compiled as of now, fixing it would be extremely beneficial for users who self-compile, because CFI is a very significant and important feature.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Chromium CFI
2021-10-15 20:37 [ISSUE] Chromium CFI anon-lestat
@ 2021-10-15 22:19 ` q66
2021-10-15 22:19 ` [ISSUE] [CLOSED] " q66
` (6 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: q66 @ 2021-10-15 22:19 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 193 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/33579#issuecomment-944773750
Comment:
if it's not an actual build option, it's not supported
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [ISSUE] [CLOSED] Chromium CFI
2021-10-15 20:37 [ISSUE] Chromium CFI anon-lestat
2021-10-15 22:19 ` q66
@ 2021-10-15 22:19 ` q66
2021-10-16 9:05 ` anon-lestat
` (5 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: q66 @ 2021-10-15 22:19 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
Closed issue by anon-lestat on void-packages repository
https://github.com/void-linux/void-packages/issues/33579
Description:
Chromium on void linux has broken CFI with LLVM 12.0.1.
As illustrated by its template starting with line 225:
# segfaults with llvm-12.0.1
'is_cfi=false'
'use_thin_lto=false'
'use_cfi_icall=false'
'chrome_pgo_phase=0'
Even if it cant be compiled as of now, fixing it would be extremely beneficial for users who self-compile, because CFI is a very significant and important feature.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Chromium CFI
2021-10-15 20:37 [ISSUE] Chromium CFI anon-lestat
2021-10-15 22:19 ` q66
2021-10-15 22:19 ` [ISSUE] [CLOSED] " q66
@ 2021-10-16 9:05 ` anon-lestat
2021-10-16 18:28 ` q66
` (4 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: anon-lestat @ 2021-10-16 9:05 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 238 bytes --]
New comment by anon-lestat on void-packages repository
https://github.com/void-linux/void-packages/issues/33579#issuecomment-944884709
Comment:
@q66 wdym its not an actual build option? Its supposed to be there but LLVM is breaking it.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Chromium CFI
2021-10-15 20:37 [ISSUE] Chromium CFI anon-lestat
` (2 preceding siblings ...)
2021-10-16 9:05 ` anon-lestat
@ 2021-10-16 18:28 ` q66
2021-10-16 18:40 ` anon-lestat
` (3 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: q66 @ 2021-10-16 18:28 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 432 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/33579#issuecomment-944976808
Comment:
it's not an xbps-src build option (maybe learn about those before talking shit behind my back on discord), so we don't support it, we don't and can't support random combos that users might patch in and we are also not responsible for compiler crashes that arise from unsupported configurations
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Chromium CFI
2021-10-15 20:37 [ISSUE] Chromium CFI anon-lestat
` (3 preceding siblings ...)
2021-10-16 18:28 ` q66
@ 2021-10-16 18:40 ` anon-lestat
2021-10-16 18:53 ` anon-lestat
` (2 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: anon-lestat @ 2021-10-16 18:40 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 639 bytes --]
New comment by anon-lestat on void-packages repository
https://github.com/void-linux/void-packages/issues/33579#issuecomment-944979413
Comment:
@q66 okay so. I wasnt talking shit haha, i called u a bastard sure and im sorry if you took it the wrong way but i didnt mean it to be insulting. CFI comes with chromium [link](https://www.chromium.org/developers/testing/control-flow-integrity).
U can see them being disabled in chromium template line 225 because atm llvm breaks it.
chromium template starting line 225:
segfaults with llvm-12.0.1
'is_cfi=false'
'use_thin_lto=false'
'use_cfi_icall=false'
'chrome_pgo_phase=0'
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Chromium CFI
2021-10-15 20:37 [ISSUE] Chromium CFI anon-lestat
` (4 preceding siblings ...)
2021-10-16 18:40 ` anon-lestat
@ 2021-10-16 18:53 ` anon-lestat
2021-10-16 18:57 ` q66
2021-10-22 14:02 ` Vaelatern
7 siblings, 0 replies; 9+ messages in thread
From: anon-lestat @ 2021-10-16 18:53 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 261 bytes --]
New comment by anon-lestat on void-packages repository
https://github.com/void-linux/void-packages/issues/33579#issuecomment-944982861
Comment:
https://github.com/archlinux/svntogit-packages/commit/bfe890af9382031a5ea33e7552385952cd0f8077
arch for example
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Chromium CFI
2021-10-15 20:37 [ISSUE] Chromium CFI anon-lestat
` (5 preceding siblings ...)
2021-10-16 18:53 ` anon-lestat
@ 2021-10-16 18:57 ` q66
2021-10-22 14:02 ` Vaelatern
7 siblings, 0 replies; 9+ messages in thread
From: q66 @ 2021-10-16 18:57 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/33579#issuecomment-944983688
Comment:
it's disabled because it's broken, and supported on exactly 1 architecture and 1 compiler, and requires the whole thing to be built with LTO, and additionally you're using a libc officially unsupported by chromium
so, this is a wontfix from our side
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Chromium CFI
2021-10-15 20:37 [ISSUE] Chromium CFI anon-lestat
` (6 preceding siblings ...)
2021-10-16 18:57 ` q66
@ 2021-10-22 14:02 ` Vaelatern
7 siblings, 0 replies; 9+ messages in thread
From: Vaelatern @ 2021-10-22 14:02 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 649 bytes --]
New comment by anon-lestat on void-packages repository
https://github.com/void-linux/void-packages/issues/33579#issuecomment-944979413
Comment:
@q66 okay so. I wasnt talking shit haha, i called u a bastard sure and im sorry if you took it the wrong way but i didnt mean it to be insulting. CFI comes with chromium [link](https://www.chromium.org/developers/testing/control-flow-integrity).
U can see them being disabled in chromium template line 225 because atm llvm breaks it.
chromium template starting line 225:
```
segfaults with llvm-12.0.1
'is_cfi=false'
'use_thin_lto=false'
'use_cfi_icall=false'
'chrome_pgo_phase=0'
```
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2021-10-22 14:02 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-10-15 20:37 [ISSUE] Chromium CFI anon-lestat
2021-10-15 22:19 ` q66
2021-10-15 22:19 ` [ISSUE] [CLOSED] " q66
2021-10-16 9:05 ` anon-lestat
2021-10-16 18:28 ` q66
2021-10-16 18:40 ` anon-lestat
2021-10-16 18:53 ` anon-lestat
2021-10-16 18:57 ` q66
2021-10-22 14:02 ` Vaelatern
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).