What is pex_run
I've got collect2 finding a linker error and I'm out of other options so I'm poking around in the collect2 sources. I'm wondering what pex_run is (since it's getting handed the arguments this might mater?) I figure if I can get collect2 to spill its guts about what arguments are fed to "ld" I'll have at least a chance figuring out what in the bleep is going on... alternate debugging strategies are welcome. Thanks, Gary CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and contains information that is confidential and proprietary to Ampere Computing or its subsidiaries. It is to be used solely for the purpose of furthering the parties' business relationship. Any unauthorized review, copying, or distribution of this email (or any attachments thereto) is strictly prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto.
Re: What is pex_run
On Thu, Feb 25, 2021 at 09:57:55PM +, Gary Oblock via Gcc wrote: > I've got collect2 finding a linker error and I'm out of > other options so I'm poking around in the collect2 > sources. I'm wondering what pex_run is (since it's > getting handed the arguments this might mater?) See libiberty/pex-common.c. Marek
Re: HELP: MIPS PC Relative Addressing
On Thu, 25 Feb 2021, Jiaxun Yang wrote: > > > I'll take this approach first, add "lla, dlla" pseudo-instructions to > > > assembler and seeking optimization > > > in future. > > > > The DLA and LA macros are supposed to do that already, no need to invent > > new names. > > Hmm, how could we tell if the symbol is local? > Global symbols still needs to be load from GOT. Just do what all the other MIPS/GAS macros do in this situation. GAS knows whether a given symbol is local or external. > I saw RISC-V dealt that by “lla” pesudo-op which indicate the symbol is local. But RISC-V is not MIPS. Despite the similarities in the ISA its assembly language and psABI conventions are subtly different throughout. > > > Btw I found we don't have any document for MIPS pseudo-instructions. > > > RISC-V > > > put them in ISA manual > > > but it is not the case for MIPS. Is it possible to have one in binutils? > > > > There are MIPS assembly language books available; I'm fairly sure Dominic > > Sweetman's "See MIPS Run" has a chapter (I don't have the book at hand). > > I don't think GNU binutils documentation is supposed to describe the > > assembly dialects supported, except maybe for GNU extensions (pseudo-ops). > > Yeah I saw See MIPS Run, but it's not a mandatory specification. > Without a specification we may have different implementation across > toolchains and trouble users. I do not oppose a normative document, though there are ISAs for which several independently developed assembly dialects exist (e.g. x86). Traditionally GAS was meant as an assembler solely for GCC output, so it used to be adapted as a need arose. Having a formal specification would hinder such quick adaptation. I think we need to weigh pros and cons carefully. NB most macros date back to the IRIX if not MIPSCO compiler. Semantics has been documented in books and is pretty straightforward to apply in a mechanical manner to new machine instructions that need macroisation. Maciej
gcc-8-20210225 is now available
Snapshot gcc-8-20210225 is now available on https://gcc.gnu.org/pub/gcc/snapshots/8-20210225/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 8 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch releases/gcc-8 revision 76f61194f5ac61eb75b92d422e24ce30a6cddf8a You'll find: gcc-8-20210225.tar.xzComplete GCC SHA256=6c5f889ce8889cada581fcc1f4798c971e20d56bc83ce36d36c1263c6a0f807f SHA1=bcc5040d3d96fc53550f491f4d3546508cbd6319 Diffs from 8-20210218 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-8 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
Re: What is pex_run
On Thu, Feb 25, 2021 at 5:26 PM Gary Oblock via Gcc wrote: > > I've got collect2 finding a linker error and I'm out of > other options so I'm poking around in the collect2 > sources. I'm wondering what pex_run is (since it's > getting handed the arguments this might mater?) > I figure if I can get collect2 to spill its guts > about what arguments are fed to "ld" I'll have > at least a chance figuring out what in the bleep > is going on... alternate debugging strategies > are welcome. collect2 will dump out a lot of extra information and save temporary files if passed "-debug" option to collect2 (not to GCC). In other words $ gcc -Wl,-debug -o foo foo.o Thanks, David
Re: Constraints and branching in -fanalyzer
Hi, I have implemented the discussed change, bootstrapped, and run the testsuite. I would be submitting except to my disappointment I saw failures increase by 4. As it turns out, these "failures" are actually passes that had been marked "xfail" and "TRUE" "desired" in the testsuite. The items in question are in testsuite files gcc.dg/analyzer/operations.c and params.c. In particular operations.c is only partially fixed because, as I have described, I thus far have only added cases for PLUS and MINUS. As you can see in that test file, you have some tests involving multiplication and division. My question is, before bothering to submit would you like me to just add handlers for these? I guess it will save us a patch cycle. Also, your comment regarding overflows is well taken, but I think we should fix the overall problem first, then worry about the overflow corner case. Brian
