[workspace issue] Error: invalid register after refactor under workspace

[PeterWrighten]

Problem

The same issue as rust #93151.

When I want to refactor an OS project with Cargo workshop, which its original rust code is not encapsulated under cargo workspace but could promise successful run , compiler reported 'invalid register' issue as follow:

(My code is here, refactored by Cargo workspace)

% cargo build
   Compiling user_lib v0.1.0 (/Users/apple/GitHub/OperatingSystem/peter_batch_os/user)
error: invalid register `x10`: unknown register
 --> user/src/syscall.rs:9:13
  |
9 |             inlateout("x10") args[0] => ret,
  |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: invalid register `x11`: unknown register
  --> user/src/syscall.rs:10:13
   |
10 |             in("x11") args[1],
   |             ^^^^^^^^^^^^^^^^^

error: invalid register `x12`: unknown register
  --> user/src/syscall.rs:11:13
   |
11 |             in("x12") args[2],
   |             ^^^^^^^^^^^^^^^^^

error: invalid register `x17`: unknown register
  --> user/src/syscall.rs:12:13
   |
12 |             in("x17") id
   |             ^^^^^^^^^^^^

error: could not compile `user_lib` due to 4 previous errors

My source code here has added unsafe statement and asm mod, target triple is also modified to "riscv64gc-unknown-none-elf", but it seems that stil could't work under cargo workspace :(

Steps

No response

Possible Solution(s)

No response

Notes

No response

Version

cargo 1.60.0-nightly (2022-01-18)

[PeterWrighten]

Now it works well by changing rustflags, but still cound not guarantee its performance when .cargo config file is not under root directory. I want to know how could I do to work it out just depended by .cargo file under members' crate.

[bjorn3]

.cargo/config.toml is read for the current directory and all of it's parent directories. It isn't necessarily read for the specific workspace member you are trying to build if you are not in it's directory.

[PeterWrighten]

.cargo/config.toml is read for the current directory and all of it's parent directories. It isn't necessarily read for the specific workspace member you are trying to build if you are not in it's directory.

But actually, in my case, if .cargo/config.toml is just in members' crate (In my code, it is ./user/.cargo/config.toml) but not in peter_batch_os directory, it couldn't be built at all...

[ehuss]

I'm going to close as this sounds like an issue with config file search order. Those issues are tracked in #9769. There are a few other workarounds, some of them unstable (such as per-package-target and profile rustflags).