Gunther Nikl <[EMAIL PROTECTED]> writes:
> This PR is about missing USER_LABEL_PREFIX for static variables. The issue
> was fixed for 4.0, but for 3.4 there won't be a fix as stated in the audit
> trail by Mark Mitchell in comment #15. He probably based his decision on
> comment #14, where Geoff K
"Domagoj Flanks" <[EMAIL PROTECTED]> writes:
> Where're these flags defined in 4.0.2?
>
> flag_syntax_only
> flag_mudflap
They are defined in the file common.opt.
Ian
"Domagoj D" <[EMAIL PROTECTED]> writes:
> Does GCC front- and middle-end keep the source code line numbers all
> the way until the RTL is generated? I'd need that for the tool I'm
> developing.
Yes. They have to, in order to generate correct debugging
information.
> Also, are there any simple s
Gerald Pfeifer <[EMAIL PROTECTED]> writes:
> Is anyone seeing this? With current 4.1 sources, on a machine with "only"
> 1GB of main memory + 1GB swap, the following part of `make install`
>
> Adding java source files from srcdir '/cvs/gcc/trunk/libjava/classpath'.
> Adding java source files
Mark Mitchell <[EMAIL PROTECTED]> writes:
> There is one advantage I see in the LTO design over LLVM's design. In
> particular, the LTO proposal envisions a file format that is roughly at
> the level of GIMPLE. Such a file format could easily be extended to be
> at the source-level version of Tr
[EMAIL PROTECTED] (Jack Howarth) writes:
> Where exactly are the compiler flags new to gcc 4.1.0 described.
http://gcc.gnu.org/gcc-4.1/changes.html
Ian
Eric Fisher <[EMAIL PROTECTED]> writes:
> Firstly, shall I support it in the machine.md file, or just leave it to
> libgcc?
> Dose the libgcc support it if I don't implement in the machine.md file?
Yes, if you supply SImode operations, libgcc will give you some DImode
operations, and the others
DJ Delorie <[EMAIL PROTECTED]> writes:
> Reload 0: reload_in (HI) = (plus:HI (reg/f:HI 7 fb)
> (const_int -128))
> A_REGS, RELOAD_OTHER (opnum = 0)
> reload_in_reg: (plus:HI (reg/f:HI 7 fb)
> (const_int -128))
>
Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
> Does GCC support any target where the object representation of a
> fundamental type T (e.g. int, float, double, pointers) whose all bits
> are zero does not hold value (T)0?
Surprisingly, the answer seems to be yes. For the C4X target, a
single pr
DJ Delorie <[EMAIL PROTECTED]> writes:
> > It does seem like reload 0 should be RELOAD_FOR_ something _ADDR.
> > What set it to RELOAD_OTHER?
>
> Ok, we start with a RELOAD_OTHER for the zero_extendhisi.
I'm not clear on why that happens. Most reloads start out as
RELOAD_FOR_INPUT or RELOAD_FOR
Andrew Haley <[EMAIL PROTECTED]> writes:
> On i386 we replace (add sp -4) with (push reg). This generates faster
> and smaller code.
>
> However, we are not copying RTX_FRAME_RELATED_P from the old
> instructions to the new, and so we are not emitting unwind information
> for the stack pointer a
Andrew Haley <[EMAIL PROTECTED]> writes:
> The problem that is bugging me is if there is more than one
> instruction in the repleacement sequence, which one do you copy the
> REG_FRAME_RELATED_EXPR to?
I think an algorithm which should work fairly reliably in the general
case is:
1) Are there
Eric Fisher <[EMAIL PROTECTED]> writes:
> I'd like to know since gcc implicitly call memset function to perform
> optimization and my c libraries are unusable for now. Can I take
> another way? Say don't call memset. How to do that?
In your tm.h file define CLEAR_BY_PIECES_P to always return 1.
(
Liu Haibin <[EMAIL PROTECTED]> writes:
> Hi,
>
> I got a dump of sha.c.27.flow2 from gcc 3.4.1. I don't quite
> understand the LOG_LINKS of insn 498. LOG_LINKS in insn 498 shows that
> it has a data dependence (a read after write dependence) with insn 3.
> Why is it so? I don't see any dependence
Liu Haibin <[EMAIL PROTECTED]> writes:
> I'd doing some coding right before peephole2 pass. I'd like to have a
> function that takes rtl as input and returns the values of register
> inputs, register output and operator. For example,
>
> input:
> (insn 496 34 29 1 (set (reg/f:SI 3 r3 [235])
>
Matt Ritchie <[EMAIL PROTECTED]> writes:
> Basically make it even more crossplatform compiliant
> and emulator friendly
> eg: add the following cpu series : 8080, z80, 6502,
> 6800, and cpm/8000? :)
gcc is driven by volunteer efforts and by paid efforts. The way to
get gcc to support these targe
Hans-Peter Nilsson <[EMAIL PROTECTED]> writes:
> On Mon, 19 Dec 2005, Richard Henderson wrote:
> > I think that this is all complicated enough that we should
> > simply deny peepholing insns with RTX_FRAME_RELATED_P set.
>
> I was just bitten by the same behavior for define_split.
> Should the sa
Liu Haibin <[EMAIL PROTECTED]> writes:
> Can someone help me explain that why there's an REG_DEP_OUTPUT (write
> after write dependence) between jump_insn 547 and insn 82?
>
> (insn 82 543 478 3 (set (mem/s:SI (reg/f:SI 6 r6 [224]) [4 W S4 A32])
> (reg:SI 2 r2 [95])) 8 {movsi_internal} (i
Kenneth Zadeck <[EMAIL PROTECTED]> writes:
> 1) Do you believe that this code could be correct?
Well, no.
> 2) Most of the paragraphs are protected by either reload_completed or
> epilogue_completed (which has a comment at the its point of
> declaration that it is true for both the prologue and
Kenneth Zadeck <[EMAIL PROTECTED]> writes:
> > For complete accuracy, there are probably going to be some target
> > specific registers which need to be handled, unfortunately. For
> > example, on MIPS, with -mabicalls (which is the default on GNU/Linux),
> > $25 is live on function entry. It ho
Stuart Hastings <[EMAIL PROTECTED]> writes:
> Regarding
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11135
>
> How much effort would it take to fix this, at least for x86 (32-bit)?
Not hard. See the MIPS backend, for example. Look at how it defines
PIC_OFFSET_TABLE_REGNUM and how it
DJ Delorie <[EMAIL PROTECTED]> writes:
> > I have observed the following behavior while using "float" and
> > "double" data types for m16c target. Any computation involving a
> > "float" or a "double" data type does not work on the m16c hardware.
> > However, the correct values can be observed usi
DJ Delorie <[EMAIL PROTECTED]> writes:
> > I don't know whether any other chip has this particular limitation,
> > but it's not hard to handle. ashlsi3 and friends should be a
> > define_expand which turn an overly large CONST_INT into two shifts,
> > load the shift count into a register, whichev
Perry Smith <[EMAIL PROTECTED]> writes:
> The problem: In the particular build I am trying to do, when
> libgcc2.c is compled with -DL_floatdidf, instead of defining a
> routine called _floatdidf or __floatdidf, it creates a routine called
> __floattidf which references __floatdidf.
...
> This i
DJ Delorie <[EMAIL PROTECTED]> writes:
> reg_overlap_mentioned_for_reload_p() assumes that all SUBREGs
> have REGs as their operand. However, register_operand() has
> this comment:
>
>(Ideally, (SUBREG (MEM)...) should not exist after reload,
>but currently it does result from (S
DJ Delorie <[EMAIL PROTECTED]> writes:
> > Reload can temporarily produce a SUBREG of a MEM if, as the comment
> > says, the insn has a SUBREG of a REG, and the REG is turned into a
> > memory address. But before approving this patch, can you say
> > something about what calls reg_overlap_mention
Jason Merrill <[EMAIL PROTECTED]> writes:
> Remind me why it's a good idea to force me to mess with bootstrapping
> at all, when all I want is to build a copy of the compiler that I can
> use for debugging problems? There has to be an easier way to do that.
> My laptop builds stage1 reasonably fa
"John David Anglin" <[EMAIL PROTECTED]> writes:
> I have a question about storage for uninitialized objects.
>
> I made the mistake of looking at the code being generated for
> testcase #2 in http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24626.
> I noticed that reload used the same register r3 for
Paul Schlie <[EMAIL PROTECTED]> writes:
> As a simple example, although x may be indeterminate -1 < sin(x) < +1
> is unconditionally true, as must be tan(x) = sin(x)/cos(x), and x^x = 0;
No, the ISO C standard is clear that an uninitialized variable may be
set to a trap representation (6.7.8,
Paul Schlie <[EMAIL PROTECTED]> writes:
> Given that it would appear that the only time the compiler may attempt
> to optimize the allocation/use of an un-initialized variable, is when it
> knows for certain it hasn't been initialized; might it be preferable to
> then assign it a deterministic che
DJ Delorie <[EMAIL PROTECTED]> writes:
> Two copies of gcc, both configured for the same target and built from
> the same sources, should produce identical objects regardless of how
> they are built or what they run on.
But note that we do not satisfy this today. Specifically if you build
gcc on
"H. J. Lu" <[EMAIL PROTECTED]> writes:
> 2006-01-16 H.J. Lu <[EMAIL PROTECTED]>
>
> * fold-const.c (fold_minmax): Always initialize compl_code.
>
> --- gcc/fold-const.c.foo 2006-01-16 11:33:31.0 -0800
> +++ gcc/fold-const.c 2006-01-16 11:56:13.0 -0800
> @@ -7191,14
ZengNan <[EMAIL PROTECTED]> writes:
> (define_insn ""
> [(set (match_operand:CCFP 0 "register_operand" "=z")
> (match_operator:SF 1 "signed_comparison_operator"
> [(match_operand:SF 2 "register_operand" "f")
> (match_operand:SF 3 "register_operand" "f")]))]
> ""
>
I'm trying to merge trunk revision
7c46e71d016c86971ac26c6fa38d76482859f296 to the gccgo branch. I did
this by checking out the branch ("git checkout origin/devel/gccgo")
and running "git merge master".
I'm not sure whether I should keep reporting this kind of operation to
gcc-patches now that we
On Wed, Jan 22, 2020 at 10:39 AM Joseph Myers wrote:
>
> On Wed, 22 Jan 2020, Ian Lance Taylor wrote:
>
> > I don't want to send 581 e-mails. I would be happy not sending any
> > e-mails at all. I would also be happy sending 1 e-mail.
>
> This is the i
FX writes:
> 1. It appears that even on platforms with BACKTRACE_SUPPORTED == 0
> (such as x86_64-apple-darwin), libbacktrace is built and able to
> perform a nonsymbolic backtrace (which appears accurate). Is that a
> feature? Can I rely on it?
Yes, that is a feature. You should always get acc
On Thu, Aug 13, 2015 at 7:11 AM, FX wrote:
>
>> I don't know why this is not working. Everything looks fine in the
>> a.out that you sent. Unfortunately, I think you sent the one built
>> without libbacktrace. Can you send me the one built with libbacktrace?
>
> Attached is the a.out with libgf
On Thu, Aug 13, 2015 at 8:25 AM, Ian Lance Taylor wrote:
> On Thu, Aug 13, 2015 at 7:11 AM, FX wrote:
>>
>>> I don't know why this is not working. Everything looks fine in the
>>> a.out that you sent. Unfortunately, I think you sent the one built
>>> w
On Thu, Aug 13, 2015 at 8:50 AM, FX wrote:
>> And yet, that patch has absolutely nothing to do with libbacktrace.
>> Hmmm. Let's try this one.
>
> Works perfectly with the patch:
Patch tested and committed with this ChangeLog entry.
2015-08-13 Ian La
On Wed, Aug 26, 2015 at 12:41 PM, Jeff Law wrote:
> On 08/26/2015 01:31 PM, Eric S. Raymond wrote:
>>>
>>> mib = mib
>
> Michael Bushnell. Aagain, not active in forever. m...@geech.gnu.ai.mit.edu
> probably doesn't work anymore.
This person (not quite sure how to say this) changed his name to
T
On Wed, Aug 26, 2015 at 12:31 PM, Eric S. Raymond wrote:
>
> aluchko = aluchko
Aaron Luchko (was ).
> bo = bo
Bo Thorsen (was ).
> bson = bson
Jan Brittenson (was ).
> cks = cks
Chris Smight (was ).
> click = click
You've got me on that one. Any hints?
> dennisg = dennisg
Dennis
On Wed, Aug 26, 2015 at 12:31 PM, Eric S. Raymond wrote:
>
> aluchko = aluchko
Aaron Luchko (was ).
> bo = bo
Bo Thorsen (was ).
> bson = bson
Jan Brittenson (was ).
> cks = cks
Chris Smight (was ).
> click = click
You've got me on that one. Any hints?
> dennisg = dennisg
Dennis
On Wed, Aug 26, 2015 at 1:43 PM, Jeff Law wrote:
>> fx = fx
>
> fx is active... Francois-Xavier Coudert fxcoud...@gcc.gnu.org Not sure how
> I missed that the first time around.
No, this is a different person (it's Dave Love). Francois-Xavier has
always gone by fxcoudert.
Ian
On Wed, Aug 26, 2015 at 1:35 PM, Eric S. Raymond wrote:
> root = root
Hmmm. root. This was probably Danny Berlin logged into the root
account on sourceware.
Ian
On Wed, Aug 26, 2015 at 1:54 PM, Eric S. Raymond wrote:
> Ian Lance Taylor :
>> On Wed, Aug 26, 2015 at 1:43 PM, Jeff Law wrote:
>>
>> >> fx = fx
>> >
>> > fx is active... Francois-Xavier Coudert fxcoud...@gcc.gnu.org Not sure how
>> > I
On Wed, Aug 26, 2015 at 2:29 PM, Eric S. Raymond wrote:
>
>> > rolfh = rolfh
>>
>> I think this is Arne H. Juul (was ).
>
> How did rolfh turn into arne or vice-versa? I'd like to have confirmation
> on this one.
I don't know where the user name comes from, but this one is from
multiple ChangeL
On Wed, Aug 26, 2015 at 2:43 PM, Eric S. Raymond wrote:
> Joseph Myers :
>> > cks = cks
>>
>> Chris Smith
>
> OK, we have a disagreement. Ian thinks this was
>
> cks = Chris Smight
Gah, I somehow typoed the name. Sorry. Chris Smith is correct. The
only address I have is c...@bach.convex.co
On Thu, Aug 27, 2015 at 7:38 AM, Eric S. Raymond wrote:
> I've made it available at:
>
> http://thyrsus.com/gitweb/?p=gcc-conversion.git
>
> The interesting content is gcc.map (the contributor map) and gcc.lift.
>
> Presently the only command in gcc.lift expunges the hooks directory.
Thanks for d
On Thu, Aug 27, 2015 at 3:58 PM, Joseph Myers wrote:
> On Thu, 27 Aug 2015, Eric S. Raymond wrote:
>
>> For the curios, here's what it looks like to deal with this in reposurgeon:
>>
>> authors read >
>> # Deal with the one ambiguous username.
>> (<1>..<14639> & /master/b) | /premerge-fsf-branch/b
On Tue, Sep 1, 2015 at 5:51 PM, Andy Lutomirski wrote:
>
> Linux has a handful of weird features that are only supported for
> backwards compatibility. The big one is the x86_64 vsyscall page, but
> uselib probably belongs on the list, too, and we might end up with
> more at some point.
>
> I'd l
On Sat, Sep 12, 2015 at 2:11 PM, David Kunsman wrote:
> Hello...I am thinking about starting to hack on something and I found
> https://gcc.gnu.org/wiki/Speedup_areas and one of the projects is a
> multi-threaded linker. I am just wondering if this is still an area
> of interestif it is I pl
On Sat, Sep 12, 2015 at 11:38 PM, Anders Oleson wrote:
>
> From examining the __morestack code, I found that the sigprocmask
> system call is being called (twice?!) per __morestack, even when it
> should just need to switch to the next allocated segment. I did read
> the reason for that change: to
On Wed, Sep 16, 2015 at 1:18 AM, Anders Oleson wrote:
>
> How difficult is it to modify the prologs that get generated? I think
> I found the code that does that in i386.c and i386.md, but it is
> pretty cryptic to me. Any pointers? I know exactly what I want the
> assembler to look like. If so I
On Sun, Oct 4, 2015 at 5:09 AM, Matthijs van Duin
wrote:
> On 4 October 2015 at 10:05, Andrew Haley wrote:
>> Do you have GCC copyright assignment
>
> No, but I hereby license it under the http://www.wtfpl.net/ (or, in
> any legal system which acknowledges such an act, place it in public
> domain
On Tue, Nov 24, 2015 at 8:58 AM, wrote:
>
> I'm really concerned with loosening the meaning of basic asm. I
> wish I could find the documentation that says, or implies, that it
> is a memory clobber. And/or that it is implicitly volatile.
The volatile one is right there in the current docs.
h
The bug report https://golang.org/issue/13662 describes a case in
which ivopts appears to be breaking garbage collection for the Go
compiler. There is an array allocated in memory, and there is a loop
over that array. The ivopts optimization is taking the only pointer
to the array and subtracting
On Mon, Jan 11, 2016 at 10:00 AM, Michael Matz wrote:
>
> On Fri, 8 Jan 2016, Richard Biener wrote:
>
>> > The only solution here is for ivopts to keep a pointer to the array,
>> > not a pointer to some location near, but outside of the array.
>>
>> Yes, the solution is to make IVOPTs not do this
On Tue, Jan 19, 2016 at 11:08 PM, Sriraman Tallam wrote:
>
> There is no documentation as such that I am aware of to write a linker
> plugin. Here is a very brief overview. The linker calls the
> plugin's "onload" function when registering the plugin and the plugin
> inturn can register two cal
On Fri, Feb 19, 2016 at 1:16 PM, Mark Wielaard wrote:
> On Fri, Feb 19, 2016 at 12:57:34PM -0800, H.J. Lu wrote:
>> How do I subscribe gnu-abi mailing list? The project page just
>> points to the mailing list archive. There is no option to subscribe
>> it.
>
> To subscribe sent email to gnu-abi-
On Mon, Apr 4, 2016 at 6:52 AM, Adhemerval Zanella
wrote:
>
> Since BZ#67877 [1] does not have much information on it, I would like
> to ask for some inputs of which is the requirement of implementing
> split-stack on aarch64 besides 'feature parity'.
>
> I am asking it because on PR it states the
On Fri, May 6, 2016 at 10:42 PM, Rich Felker wrote:
>
> The *context APIs are deprecated and I'm not sure they're worth
> supporting with this. It would be a good excuse to get people to stop
> using them.
The gccgo library uses them, because there is no working alternative.
In general coroutine
On Mon, May 9, 2016 at 12:35 PM, Rich Felker wrote:
> On Mon, May 09, 2016 at 09:02:33PM +0200, Michael Matz wrote:
>> Hi,
>>
>> On Sat, 7 May 2016, Rich Felker wrote:
>>
>> > > > * sigaltstack and swapcontext are broken too.
>> > >
>> > > We have prototype that supports swapcontext that we're hap
On Mon, May 9, 2016 at 12:41 PM, Joel Sherrill
wrote:
>
> On 5/9/2016 2:25 PM, Ian Lance Taylor wrote:
>>
>> On Fri, May 6, 2016 at 10:42 PM, Rich Felker wrote:
>>>
>>>
>>> The *context APIs are deprecated and I'm not sure they're worth
>
On Mon, May 9, 2016 at 12:48 PM, Joel Sherrill
wrote:
>
> On 5/9/2016 2:45 PM, Ian Lance Taylor wrote:
>>
>> On Mon, May 9, 2016 at 12:41 PM, Joel Sherrill
>> wrote:
>>>
>>>
>>> On 5/9/2016 2:25 PM, Ian Lance Taylor wrote:
>>>>
On Mon, May 9, 2016 at 1:07 PM, Joel Sherrill wrote:
>
> One complication on RTEMS which is a single process, multi-threaded RTOS
> is that we can no longer check the stack bounds. For threads, we know
> where the stack memory is and the range for each thread. For ucontext_t,
> it seems this knowl
On Mon, May 9, 2016 at 2:03 PM, Joel Sherrill wrote:
>
> On 5/9/2016 3:41 PM, Ian Lance Taylor wrote:
>>
>> On Mon, May 9, 2016 at 1:07 PM, Joel Sherrill
>> wrote:
>>>
>>>
>>> One complication on RTEMS which is a single process, multi-threade
On Wed, Jun 15, 2016 at 7:00 AM, zet wrote:
>
> I am reading the source of gcc(version 4.8.2), there is a important
> symbol 'global_options' whose type is struct gcc_options
> in cc1' entry function toplev_main().
>
> I have build the gcc with make -g -O0, in gdb use ptype i can get the
> content
On Sun, Jul 10, 2016 at 10:15 AM, Manuel López-Ibáñez
wrote:
> On 23 June 2016 at 18:02, Pedro Alves wrote:
>> But on the other hand, the idea of maintaining multiple gnulib
>> copies isn't that appealing either. Considering that the long
>> term desired result ends up with a libiberty that is n
I'm not going to reply to any specific points, but I do want to
comment that I've come to believe that e-mail based patch review is a
problem. Unfortunately, I do not foresee the GCC maintainers moving
away from it.
I believe that Diego tried setting up an alternative patch review
system using Re
On Tue, Oct 25, 2016 at 10:53 PM, Will Hawkins wrote:
>
> My name is Will Hawkins and I am a longtime user of gcc and admirer of
> the project. I hope that this is the proper forum for the question I
> am going to ask. If it isn't, please accept my apology and ignore me.
>
> I am a real geek and I
On Wed, Oct 26, 2016 at 9:31 AM, Will Hawkins wrote:
>
> Thank you for your response! I don't think that there has to be
> controversy to be interesting. Obviously that split/reunification was
> important, but I think that there might even be some value in
> documenting the minutia of the project'
On Wed, Oct 26, 2016 at 9:35 AM, Will Hawkins wrote:
>
> Can any of you recall a turning point where development went from
> being driven by hobbyists to being driven by career developers? As a
> result of that shift, has there been a change in the project's
> priorities? Have there been conflicts
On Wed, Oct 26, 2016 at 10:17 AM, Will Hawkins wrote:
>
> Wow, thanks Ian! This is awesome stuff! As I read through it, I may
> have some additional questions. If I do, would you mind if I emailed
> you directly? Thanks again for taking the time to write all this down!
> Fascinating!
I would pref
On Wed, Oct 26, 2016 at 10:28 AM, Richard Kenner
wrote:
>> The Ada frontend was developed at AdaCore.
>
> The Ada frontend was developed at NYU, as an Air Force-funded project
> to show that Ada95 (then called Ada9X) was implementable. AdaCore was
> later formed once that was complete to provide
On Thu, Oct 27, 2016 at 6:08 AM, Anthony Green wrote:
> Is it still important that libffi be included in the GCC tree?
[ Replying again as last message was bounced as HTML--sorry for the
duplication.]
libffi is used by libgo, for much the same reason as it was used by
libjava, so it needs to com
On Tue, Nov 1, 2016 at 2:01 PM, Josh Conner wrote:
> My apologies in advance for the spam if this isn't the right forum. I
> had svn access in a former life (jcon...@apple.com), and I'm trying to
> restore my access for my new employer. I sent an email to overseers
> last week, but haven't heard b
On Thu, Nov 3, 2016 at 7:20 PM, Lei Wang wrote:
> The brief structure of libgcc/crtstuff.c is as follows:
>
> #ifdef CRT_BEGIN
> …
> #elif defined(CRT_END)
> ...
> # ifdef OBJECT_FORMAT_ELF
> …
> # else
>
> static void
> __do_global_ctors_aux (void)/* prologue goes in .text section */
> {
>
On Fri, Nov 4, 2016 at 7:55 AM, lei wang wrote:
>
> In fact, I just want to find a practical way to make the crt work.
> Currently, I did the following configure in my port:
>
> include "elfos.h" in tm.h
> define HAS_INIT_SECTION
> undefine OBJECT_FORMAT_ELF
> define INVOKE__main
> use default INI
On Fri, Nov 4, 2016 at 8:12 AM, lei wang wrote:
>
> Thanks. One more question, my current entry point of the program is
> main, after which there is a call to __main to do the constructor
> stuffs and register destructors. Without INVOKE__main, which point
> should I define as the entry?
You shou
On Tue, Apr 22, 2014 at 9:38 AM, Solal wrote:
>
> I've got ideas for improve the preprocessor with specific features.
>
> The basic idea is to make the preprocessing language a complete
> programming language.
We are very unlikely to add such features to GCC unless they first
become part of the C
On Fri, Apr 25, 2014 at 11:27 AM, Umesh Kalappa
wrote:
>
> In our private port ,we define function_arg hook to pass the first
> three args in the reg and rest will go to stack.
>
> But for variadic functions the arguments need to pass through the stack.
>
> How we can achieve this ?? Any inp
I'm very pleased to report that, thanks to the hard work of Chris
Manghane, the Go frontend no longer includes any header files from
GCC. This means that global changes to the GCC middle-end no longer
need to touch any files in gcc/go/gofrontend. Instead, they will only
need to modify files in gc
On Fri, May 16, 2014 at 4:47 AM, Kirill Yukhin wrote:
>
> To support the offloading features for Intel's Xeon Phi cards
> we need to add a foreign library (liboffload) into the gcc repository.
> README with build instructions is attached.
Can you explain why this library should be part of
On Fri, May 16, 2014 at 6:34 AM, Sheheryar Zahoor Qazi
wrote:
>
> I am trying to provide soft-fp support to a an 18-bit soft-core
> processor architecture at my university. But the problem is that
> libgcc has not been cross-compiled for my target architecture and some
> functions are missing so i
On Tue, May 20, 2014 at 7:37 AM, Sheheryar Zahoor Qazi
wrote:
>>>If you have a working compiler that is missing some functions
>>>provided by libgcc, that should be sufficient to build libgcc.
> Meaning that even if i am unable build libgcc to my new architecture,
> I should be able to able to pro
On Tue, May 20, 2014 at 7:18 AM, Dmitry Antipov wrote:
>
> I'm trying to support -fsplit-stack in GNU Emacs. The most important problem
> is that
> GC uses conservative scanning of a C stack, so I need to iterate over stack
> segments.
> I'm doing this by using __splitstack_find, as described in
On Wed, May 21, 2014 at 6:13 AM, Sheheryar Zahoor Qazi
wrote:
>>>Building libgcc is not optional. It is required for all targets.
>
> So, irrespective whether i provide floating point implementation by
> soft-fp, fpu-bit or ieeelib, an error free libgcc build is a MUST?
Yes.
> What if I dont wa
On Tue, May 20, 2014 at 10:30 PM, Dmitry Antipov wrote:
>
> The next major problem is that -fsplit-stack code randomly crashes with the
> useless gdb backtrace, usually pointing to the very beginning of the
> function
> (plus occasional "Cannot access memory at..." messages), e.g.:
>
> (gdb) bt 1
On Mon, Jun 2, 2014 at 12:18 AM, Mike Izbicki wrote:
>> Though for the gory details and authoritative answers I suppose you'd
> have to look into the source code.
>
> Where would I find the code for this?
This is the GCC source code. There isn't one file that implements
-ffast-math. -ffast-math
On Tue, Jun 10, 2014 at 3:30 AM, Anonymous User
wrote:
>
> I'd like to help with the modularization of GCC.
>
> I've visited the getting started page at the official wiki but its contents
> seem too old. I'm fairly new to GCC and and I'm bewildered by its huge code
> base with lengthy and complica
On Tue, Jun 10, 2014 at 7:54 AM, Dmitry Antipov wrote:
> On 05/21/2014 06:10 PM, Ian Lance Taylor wrote:
>
>> I'm sorry, I have nothing useful to suggest. I agree that that sounds
>> like a stack overflow, which should in general be impossible with
>> -fsplit-stack w
On Thu, Jul 10, 2014 at 11:40 AM, Franzi Edo. wrote:
>
> As for the version 4.9.0, on OSX stil remain a problem.
> I cannot build an ARM a cross compiler!
> Here is the message (same as for the 4.9.0)
>
> ...
> .../Packages/gcc-4.9.1/gcc/config/arm/neon.md:3486:10917: fatal error:
> bracket
On Wed, Jul 23, 2014 at 3:28 AM, Jason Merrill wrote:
> On 07/20/2014 06:01 PM, Jakub Jelinek wrote:
>>
>> On Sun, Jul 20, 2014 at 05:59:08PM +0100, Richard Biener wrote:
>>>
>>> I understood we agreed on 5.0 and further 5.1, 5.2 releases from the
>>> branch and 6.0 a year later. With unspecified
On Thu, Jul 31, 2014 at 4:52 AM, NightStrike wrote:
>
> One thing you might want to consider is that with the typical X.Y.Z
> versioning of most GNU projects, changing X allows breaking
> compatibility in a significant way with previous versions. While Z
> fixes regressions and Y adds new feature
On Tue, Jul 29, 2014 at 10:27 AM, Markus Trippelsdorf
wrote:
> On 2014.07.29 at 19:14 +0200, Richard Biener wrote:
>> On July 29, 2014 6:45:13 PM CEST, Eric Botcazou
>> wrote:
>> >> I think that if anybody has strong objections, now is the time to
>> >make
>> >> them. Otherwise I think we shoul
On Tue, Jul 29, 2014 at 9:45 AM, Eric Botcazou wrote:
>> I think that if anybody has strong objections, now is the time to make
>> them. Otherwise I think we should go with this plan.
>
> IMHO the cure is worse than the disease.
What do you propose that we do?
>> Given that there is no clear r
On Thu, Jul 31, 2014 at 4:22 PM, Ed Smith-Rowland <3dw...@verizon.net> wrote:
> On 07/31/2014 07:03 PM, Ian Lance Taylor wrote:
>>
>> I believe the GCC project has become too large to be able to usefully
>> speak about breaking compatibility with previous versions. Ther
On Tue, Jul 29, 2014 at 11:35 AM, David Malcolm wrote:
>
> At Cauldron on the Sunday morning there was a Release Management BoF
> session, replacing the specRTL talk (does anyone know what happened to
> the latter?)
The specRTL presenter had to leave early for personal reasons.
Ian
On Tue, Aug 5, 2014 at 4:54 AM, Dmitry Antipov wrote:
>
> it it possible to get a kind of diagnostics if the variable
> is totally optimized away? For example, in:
>
> void foo (struct some_type *obj) {
> ... some code where 'obj' is not used ...
> bar (obj->some_member);
> ... some code wh
On Fri, Aug 15, 2014 at 12:48 AM, Alexander Shopov wrote:
>
> The symbol/assembler name (I do not know what is the right word) that
> is generated in the .h header file is:
> extern int Cgoexp_Dummy (int p0)
> __asm__("cgo_problem_example_com_demo.Cgoexp_Dummy");
>
> The symbol that exists in the
601 - 700 of 3176 matches
Mail list logo
