Hi all, I'm working on the RISC-V port of V8. It would be very useful for us to have a way to separate the test expectations for the architectures we cover in separate *-riscv.status files, so we can change them without the risk of breaking things for others. Given the OWNER setup we're using, this will also allow us to avoid pestering core team members with small status file updates :)
It shouldn't be too hard to add support for some level of modularity to the status file support, but clearly it comes with the cost of having to worry about multiple places to find the status for a specific test. Maybe that cost and the extra complexity in the status file parser outweigh the benefits. One way of doing it would be to allow importing other status files with extra conditions implicitly added to the imported statuses - and another would be to check that all conditions in the imported statuses satisfy the import arch requirements: ['arch in [riscv32, riscv64]', IMPORT, 'mjsunit-riscv.status'] Thoughts? Regards, Kasper -- -- v8-dev mailing list [email protected] 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/v8-dev/CAKaTMyLW-%2BVERD0iQ2k-pbRNGZqBZUO5QTa%2BNOFYvk0dh5z%2BFw%40mail.gmail.com.
