| 19 Aug 2025 |
 emily | so maybe that's okay. | 22:59:21 |
| 20 Aug 2025 |
|  jopejoe1 (4094@39c3) changed their display name from jopejoe1 (4094@GPN23) to jopejoe1. | 18:50:45 |
| 21 Aug 2025 |
|  Theo Paris joined the room. | 22:11:07 |
| 23 Aug 2025 |
 John Ericson | emily: https://clang.llvm.org/docs/Multilib.html oh ok, it looks like this YAML is the proper way to make a multi-target wrapped compiler | 00:36:49 |
| emily | that's for multilib variants of a single architecture? which is quite different | 00:37:35 |
| emily | the configuration files already support multi-target | 00:38:02 |
| John Ericson | emily: do the cfg file support -m flags etc afffecting which set of lookup paths it uses? | 00:38:46 |
| emily | the config files support arbitrary flags | 00:38:58 |
| emily | (that's all they support) | 00:39:00 |
| John Ericson | emily: err so as I interpret this is a way to do something like "if the user specifies --target=..... then inject -L ....." | 00:59:53 |
| John Ericson | not just a static set of flags | 01:00:00 |
| emily | but config files already offer that? they key on the target | 01:00:11 |
| John Ericson | the the conditions are more semantic than syntactic | 01:00:11 |
| John Ericson | can they key off -march and whatnot too? | 01:00:31 |
| emily | have you read the docs for the configuration files? they key on both target and language | 01:00:32 |
| emily | I don't think so, but our wrappers also don't do that | 01:00:42 |
| John Ericson | (other ways of doing target in effect?) | 01:00:43 |
| emily | -march is separate from the target | 01:00:54 |
| John Ericson | yeah I was thinking about how there was that PR for hacking multi arch in CC wrapper for buildingl inux | 01:01:03 |
| emily |
| 01:01:11 |
| emily | Note that options such as --driver-mode=, --target=, -m32 affect the search algorithm. For example, the aforementioned executable called with -m32 argument will instead search for:
| 01:01:13 |
| emily | *
Note that options such as --driver-mode=, --target=, -m32 affect the search algorithm. For example, the aforementioned executable called with -m32 argument will instead search for:
| 01:01:15 |
| emily | https://clang.llvm.org/docs/UsersManual.html#configuration-files | 01:01:18 |
| John Ericson | ok cool | 01:01:25 |
| John Ericson | I guess whoever made the multilib yaml didn't know about this :D | 01:02:29 |
| emily | I think it's specifically for configuring the GCC multilib interface | 01:05:42 |
| emily | but yeah, some overlap | 01:06:02 |
| emily | maybe the multilib stuff could be useful, it seems a little baroque though | 01:06:11 |
| John Ericson | yeah all I want is the conceptual parts | 02:21:56 |
| John Ericson | -print-multi-lib itself is only for building GCC with --enable-multilib, and the whole point of GCC NG is you get the benefits from that without needing to do that | 02:22:32 |
