https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105134
--- Comment #11 from Andrew Pinski ---
(In reply to piliu from comment #10)
> (In reply to Andrew Pinski from comment #7)
> > I am trying to understand this. Is it ok to use the SSE registers inside
> > purgatory or not?
> >
>
> SSE can speed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105134
--- Comment #10 from piliu at redhat dot com ---
(In reply to Andrew Pinski from comment #7)
> I am trying to understand this. Is it ok to use the SSE registers inside
> purgatory or not?
>
SSE can speed up the program, and if possible it is su
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105134
--- Comment #9 from Andrew Pinski ---
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/purgatory/Makefile?id=1b03cf7adc3c156ecab2618acb1ec585336a3f75
was the commit to "fix" this but as I think I mentioned here it is just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105134
--- Comment #8 from Andrew Pinski ---
Looks like only ppc64 does:
ppc64_PURGATORY_EXTRA_CFLAGS += -m64 -msoft-float \
-fno-exceptions
Most likely purgatory/arch/x86_64/Makefile needs the following added the end
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105134
--- Comment #7 from Andrew Pinski ---
I am trying to understand this. Is it ok to use the SSE registers inside
purgatory or not?
Now that the vectorizer is used turned on at -O2 and above, without -mno-sse,
on x86_64 target, the vector instruct
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105134
--- Comment #6 from piliu at redhat dot com ---
Created attachment 52757
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52757&action=edit
precompiled code of sha256
compile command:
gcc -E -fno-zero-initialized-in-bss -mcmodel=large -Os -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105134
--- Comment #5 from piliu at redhat dot com ---
Created attachment 52756
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52756&action=edit
-ftree-vectorize can not produce correct code for kexec-tools
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105134
--- Comment #4 from piliu at redhat dot com ---
(In reply to Richard Biener from comment #3)
> Can you provide preprocessed source of the TU containing sha256_starts and
> the full compiler command-line used to compile it?
For a single file.
gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105134
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2022-04-04
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105134
--- Comment #2 from piliu at redhat dot com ---
More specific, the following directive beats out the bug.
diff --git a/util_lib/sha256.c b/util_lib/sha256.c
index 2e61a31..3b3e533 100644
--- a/util_lib/sha256.c
+++ b/util_lib/sha256.c
@@ -38,6 +
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105134
--- Comment #1 from piliu at redhat dot com ---
More description about the background.
There is a built file kexec-tools/purgatory/purgatory.ro, which is a tiny
bootload, compare and verify the sha256, if ok, then jump to the 2nd kernel.
The or
11 matches
Mail list logo
