On 04/04/2010 20:08, Joseph S. Myers wrote:
> I think extracting compiler/linker *internal commands* and trying to
> process or adapt them is inherently fragile and liable to break whenever
> new compiler/linker options (internal or otherwise) are added. If
> possible the aim should be to work
Hello,
I'm trying to develop a dead code finder using gcc and mozilla's
treehydra but I've hit a wall processing certain initializations of
global variables.
In order to mark a function declaration whenever its address is held
in a file scope variable/table/structure I use code like this:
-
On Mon, Apr 5, 2010 at 3:50 PM, Ehren Metcalfe wrote:
> Hello,
>
> I'm trying to develop a dead code finder using gcc and mozilla's
> treehydra but I've hit a wall processing certain initializations of
> global variables.
>
> In order to mark a function declaration whenever its address is held
> i
Hello, and a pleasant good day to everyone. With no further ado:
The process of building a simply, plain vanilla cross compiler for
arch-fmt-no_os is really probably overdone. To build, for example, a
GCC cross compiler for an i586-elf target, the build process requires
you to have a libc for the
On Mon, Apr 05, 2010 at 10:29:07AM -0430, Kofi Doku Atuah wrote:
> The process of building a simply, plain vanilla cross compiler for
> arch-fmt-no_os is really probably overdone. To build, for example, a
> GCC cross compiler for an i586-elf target, the build process requires
> you to have a libc f
On 05/04/2010 15:59, Kofi Doku Atuah wrote:
> Hello, and a pleasant good day to everyone. With no further ado:
:) Actually, that's a fair amount of ado simply to say:
> There's no *need* for a libstdc++ on a vanilla or 'bare metal' build.
This is my idea of "no further ado":
/path/to/gcc/c
Hello all!
I've put up a short diagnostics comparison between gcc, icc, and
clang. It is my plan to update this with major revisions to individual
compilers.
Included are most of the outstanding bugzilla requests with the
"diagnostic" keyword. However, I am looking for help! Please send me
cod
On 05/04/2010 16:10, Nathan Froyd wrote:
>
> Have you tried configuring with --enable-languages=c? Doing so should
> ensure that libstdc++ is not configured for your target.
I've found it possible to build a c++ compiler with no libstdc (as per other
post). Bare-metal COFF target, no libc; I
So as I mentioned in the meeting last week, I've largely been ignoring
VTA (and more generally all debugging) issues with the reload work I'm
doing. It's time to rectify that situation.
For this phase of the work (range splitting) we only need to consider a
few straightforward transformatio
On Apr 5, 2010, at 8:20 AM, Benjamin Kosnik wrote:
>
> Hello all!
>
> I've put up a short diagnostics comparison between gcc, icc, and
> clang. It is my plan to update this with major revisions to individual
> compilers.
>
> Included are most of the outstanding bugzilla requests with the
> "
On 5 April 2010 17:20, Benjamin Kosnik wrote:
>
> Hello all!
>
> I've put up a short diagnostics comparison between gcc, icc, and
> clang. It is my plan to update this with major revisions to individual
> compilers.
Awesome!
How to contribute? patches against the html? I see there are some
examp
> How to contribute? patches against the html? I see there are some
> examples without output. Also, it would be nicer if the page linked to
> each PR in bugzilla.
Well, the html is auto-generated so that isn't really the way to go.
Should I just check in the tests + xml into some gcc repository?
> 2) The clang invocations don't need -fcaret-diagnostics
> -fshow-source-location -fdiagnostics-fixit-info because they are the
> default.
>
> 3) It's best to not pass -fdiagnostics-print-source-range-info unless
> you're looking for machine interpretable output. This flag adds
> things like {3
On Apr 5, 2010, at 12:51 PM, Benjamin Kosnik wrote:
>>
>> 5) There are a couple cases of GCC rejecting valid code (e.g. 19377),
>> or which there may be some debate about (19538) it might be worth
>> pointing this out. *shrug*
>
> One of the goals was to measure the output when the input is
> t
On Apr 5, 2010, Jeff Law wrote:
> We accomplish this by emitting a load from memory into a new pseudo
> before the first use of P in a region and a store from the new pseudo
> back to memory after the last assignment to P within the region, then
> we rename all references from P to P'. It's mar
On 04/05/10 14:32, Alexandre Oliva wrote:
On Apr 5, 2010, Jeff Law wrote:
We accomplish this by emitting a load from memory into a new pseudo
before the first use of P in a region and a store from the new pseudo
back to memory after the last assignment to P within the region, then
we rena
Hi All:
I read codes in bb-reorder pass. normally it's fine to take the most
probable basic block as the downward bb.
unfortunately, the processor I'm working on is a little different.
It has no pipeline stall when branches are taken, but does introduce
stall when they are not taken.
take an exa
(Apologies to Richard for sending this twice -- I forgot to cc the list)
> At which point during the compilation does it not work? I suppose
> at the point where the qualified variants are already optimized away.
I've had some difficulty walking the DECL_INITIAL from within a
separate pass but I
On Mon, Apr 05, 2010 at 05:18:35PM -0600, Jeff Law wrote:
>> 2. When renaming references from P to P' in a region, do take debug
>> insns in the region into account, renaming references in debug insns as
>> you would in any other insn.
>>
> OK. So presumably the 2nd argument in a VAR_LOCATION
19 matches
Mail list logo
