Hi Kito, I’ve sent my assignments and my school’s disclaimer to ass...@gnu.org <mailto:ass...@gnu.org> ([gnu.org #1673033] Xing GUO), but I haven’t got response so far. Not sure if this patch can be accepted as a small bugfix patch. If not, I’m happy to wait until FSF prove it.
Best Regards, Xing > On Jan 22, 2021, at 2:26 PM, Kito Cheng <kito.ch...@gmail.com> wrote: > > Hi Xing: > > Thanks for your patch, but I would like to know did you have the > copyright assignment for FSF? or your employee/company has signed > that? > > On Thu, Jan 21, 2021 at 8:48 PM Xing GUO via Gcc-patches > <gcc-patches@gcc.gnu.org> wrote: >> >> This patch fixes -march option parsing when `p` extension exists, >> e.g., -march=rv64imafdcp should produce >> >> .attribute arch, "rv64i2p0_m2p0_a2p0_f2p0_d2p0_c2p0_p" >> >> rather than >> >> .attribute arch, "rv64i2p0_m2p0_a2p0_f2p0_d2p0_c_p" >> >> --- >> gcc/ChangeLog: >> >> * common/config/riscv/riscv-common.c >> (riscv_subset_list::parsing_subset_version): >> Fix -march option parsing when `p` extension exists. >> >> gcc/testsuite/ChangeLog: >> >> * gcc.target/riscv/attribute-18.c: New test. >> -- >> >> Cheers, >> Xing
