Bazel Rules ppc64le architecture

21 views
Skip to first unread message

James Jenkins

unread,
Oct 9, 2025, 2:06:41 PM (10 days ago) Oct 9
to v8-dev
I have a question about this commit, changing the ppc64le cpu flag mapping (https://github.com/v8/v8/commit/643348821b2a48cc43da315960a3bd6237252cc1). I know this is an older commit, I just noticed it as v8 is a dependency of the Envoy project and the version was recently bumped up.

Why was this change made? It appears to me that Bazel automatically passes “ppc” as the --cpu flag value when it is not explicitly specified, which leads me to believe that “ppc” should be the expected value of the --cpu flag. Right now, I receive `Error: key "ppc" not found in dictionary​` because of this.

Is there another way to specify the architecture that I should be using instead? Or is the preferred way to set --cpu to “ppc64”?
When I attempted to us the `v8_target_cpu​` flag with the Envoy build command, I received an error stating that the flag was unrecognized.

Any information is greatly appreciated.

Andreas Haas

unread,
Oct 15, 2025, 4:38:51 AM (4 days ago) Oct 15
to v8-...@googlegroups.com, mfar...@ibm.com

--
--
v8-dev mailing list
v8-...@googlegroups.com
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to v8-dev+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/v8-dev/e6c6129f-0c26-4eff-8e37-62985225834en%40googlegroups.com.


--

Andreas Haas

Software Engineer

ah...@google.com


Google Germany GmbH

Erika-Mann-Straße 33

80636 München


Geschäftsführer: Paul Manicle, Liana Sebastian

Registergericht und -nummer: Hamburg, HRB 86891

Sitz der Gesellschaft: Hamburg


Diese E-Mail ist vertraulich. Falls Sie diese fälschlicherweise erhalten haben sollten, leiten Sie diese bitte nicht an jemand anderes weiter, löschen Sie alle Kopien und Anhänge davon und lassen Sie mich bitte wissen, dass die E-Mail an die falsche Person gesendet wurde.

    

This e-mail is confidential. If you received this communication by mistake, please don't forward it to anyone else, please erase all copies and attachments, and please let me know that it has gone to the wrong person.


Andreas Haas

unread,
Oct 15, 2025, 8:04:29 AM (4 days ago) Oct 15
to v8-...@googlegroups.com, mfar...@ibm.com
mfar...@ibm.com told me that this question was already replied to in this thread:

And was patched here:
Reply all
Reply to author
Forward
0 new messages