For this xonly work, we are having to one-by-one find .S files that are putting data tables into the .text segment
I am hoping to find someone who can do c++ well enough, and maybe has some familiarity with the clang code, to add a warning message for this if a .long, .quad, .byte are placed into a .text section, issue a warning, then we'll be able to identify all these in a ports build and decide which need manual fixing, and move the objects into .rodata and apply __PIC__ handling as neccessary Yes, there are cases where people use .long to inject an instruction they don't believe the assembler has. We can ignore those by inspect. Can anyone help? It doesn't need to be fancy, it just needs to get us moving faster. Thanks
