GNU Tools Cauldron 2014 - Special hotel rates will expire soon
If you want to take advantage of the promotional accomodation rates at St. Catherine's college, you will need to make your reservations *soon*. Details at the conference page: http://gcc.gnu.org/wiki/cauldron2014 Thanks. Diego.
RE: jump_table_data and active_insn_p
> -Original Message-
> From: Steven Bosscher [mailto:stevenb@gmail.com]
> Sent: 05 May 2014 10:11
> To: Paulo Matos
> Cc: gcc@gcc.gnu.org
> Subject: Re: jump_table_data and active_insn_p
>
> On Mon, Mar 17, 2014 at 12:51 PM, Paulo Matos wrote:
> > Why is jump_table_data an active_insn?
> > int
> > active_insn_p (const_rtx insn)
> > {
> > return (CALL_P (insn) || JUMP_P (insn)
> > || JUMP_TABLE_DATA_P (insn) /* FIXME */
> > || (NONJUMP_INSN_P (insn)
> > && (! reload_completed
> > || (GET_CODE (PATTERN (insn)) != USE
> > && GET_CODE (PATTERN (insn)) != CLOBBER; }
> >
> > It is clear that someone [Steven Bosscher] thought it needs fixing
> but what's the problem with just removing it from the OR-expression?
>
> Places using active_insn_p, next_active_insn, prev_active_insn, etc.,
> need to be audited to make sure it's safe to remove JUMP_TABLE_DATA
> from the OR-expression.
>
> I've done most of that work, but it needs finishing and for that I
> need to find some time.
> See http://gcc.gnu.org/ml/gcc-patches/2013-11/msg03122.html
>
Fair enough.
Thanks for the explanation.
Paulo Matos
> Ciao!
> Steven
ssl support for https://gcc.gnu.org/
Hi - Thanks to help from Lisa Marie Maginnis , we now have a valid ssl/tls certificate for gcc.gnu.org, so the web server now makes https://gcc.gnu.org/* files available. Please let me/overseers know if you see any problems. One complication is the use of literal http://gcc.gnu.org/FOO";...> type data inside many of the web pages, including the front page. These should be switched to something like to make them work both with http and https. - FChE
Re: ssl support for https://gcc.gnu.org/
On Mon, 12 May 2014, Frank Ch. Eigler wrote: > One complication is the use of literal http://gcc.gnu.org/FOO";...> > type data inside many of the web pages, including the front page. These > should be switched to something like to make them work > both with http and https. I'm pretty sure most of those links are done that way so they work for the copy of the webpages on www.gnu.org (which doesn't include list archives, Bugzilla etc., and has the pages at /software/gcc/ rather than at /). They could be converted to protocol-relative links (href="//gcc.gnu.org/FOO") - that's what Wikipedia does for links that should go to http or https according to how the page with the link is being accessed - or simply all be changed to https (I don't think browsers should object to https content such as stylesheets referenced by an http page, only the other way round). -- Joseph S. Myers jos...@codesourcery.com
[GSoC] a wiki page on the gcc wiki
Dear administration of GCC Wiki, I've created an account on the gcc wiki but I don't allowed to create and edit any page. I would like to set up a wiki page to post the updates of the project after reaching my mile stones. Could you please advise me how to get appropriate rights? (I've registered as RomanGareev) -- Cheers, Roman Gareev
Re: [GSoC] questions about graphite_clast_to_gimple.c
Thank you for your answers! They saved me the time of code consideration. -- Cheers, Roman Gareev
Re: [GSoC] How to get started with the isl code generation
Hi Tobias, thank you for your advice! > On the other side, I think it is a good idea to simultaneously keep track of > the design you have in mind and the first steps you are planning to take. > Even though the full design may still need some time, > some basic decisions can probably already be taken and maybe even > implemented. Staying in some way close to the coding you will do, > may be helpful to direct your code inspections to areas of code that > will be important for your implementation. > > E.g. just setting up a second code generation in parallel that does > minimal work (generates no code at all), but that can be enabled by a > command line flag might be a first start. I agree with this. I'll start setting up a second code generation as soon as I achieve success with separate ISL AST generation. P.S.: It's still not writable. I've asked about this issue. -- Cheers, Roman Gareev
Re: [GSoC] How to get started with the isl code generation
On 12/05/2014 20:35, Roman Gareev wrote: Hi Tobias, thank you for your advice! On the other side, I think it is a good idea to simultaneously keep track of the design you have in mind and the first steps you are planning to take. Even though the full design may still need some time, some basic decisions can probably already be taken and maybe even implemented. Staying in some way close to the coding you will do, may be helpful to direct your code inspections to areas of code that will be important for your implementation. E.g. just setting up a second code generation in parallel that does minimal work (generates no code at all), but that can be enabled by a command line flag might be a first start. Hi Roman, I agree with this. I'll start setting up a second code generation as soon as I achieve success with separate ISL AST generation. what is the difference you see between ISL AST generation and code generation? What are your plans to separate the ISL AST generation? Do you foresee any difficulties/problems? Cheers, Tobias
Re: [GSoC] a wiki page on the gcc wiki
Roman Gareev wrote: I've created an account on the gcc wiki but I don't allowed to create and edit any page. I would like to set up a wiki page to post the updates of the project after reaching my mile stones. Could you please advise me how to get appropriate rights? I have added you to the edit group. Tobias
RFC: Doc update for attribute
After updating gcc's docs about inline asm, I'm trying to improve some
of the related sections. One that I feel has problems with clarity is
__attribute__ naked.
I have attached my proposed update. Comments/corrections are welcome.
In a related question:
To better understand how this attribute is used, I looked at the Linux
kernel. While the existing docs say "only ... asm statements that do
not have operands" can safely be used, Linux routinely uses asm WITH
operands. Some examples:
memory clobber operand:
http://lxr.free-electrons.com/source/arch/arm/kernel/kprobes.c#L377
Input arguments:
http://lxr.free-electrons.com/source/arch/arm/mm/copypage-feroceon.c#L17
Since I don't know why "asm with operands" was excluded from the
existing docs, I'm not sure whether what Linux does here is supported or
not (maybe with some limitations?). If someone can clarify, I'll add it
to this text.
Even without discussing "asm with operands," I believe this text is an
improvement.
Thanks in advance,
dw
Index: extend.texi
===
--- extend.texi (revision 210349)
+++ extend.texi (working copy)
@@ -3330,16 +3330,15 @@
@item naked
@cindex function without a prologue/epilogue code
-Use this attribute on the ARM, AVR, MCORE, MSP430, NDS32, RL78, RX and SPU
-ports to indicate that the specified function does not need prologue/epilogue
-sequences generated by the compiler.
-It is up to the programmer to provide these sequences. The
-only statements that can be safely included in naked functions are
-@code{asm} statements that do not have operands. All other statements,
-including declarations of local variables, @code{if} statements, and so
-forth, should be avoided. Naked functions should be used to implement the
-body of an assembly function, while allowing the compiler to construct
-the requisite function declaration for the assembler.
+This attribute is available on the ARM, AVR, MCORE, MSP430, NDS32, RL78, RX
+and SPU ports. It allows the compiler to construct the requisite function
+declaration, while allowing the body of the function to be assembly code.
+The specified function will not have prologue/epilogue sequences generated
+by the compiler; it is up to the programmer to provide these sequences if
+the function requires them. The expectation is that only Basic @code{asm}
+statements will be included in naked functions (@pxref{Basic Asm}). While it
+is discouraged, it is possible to write your own prologue/epilogue code
+using asm and use ``C'' code in the middle.
@item near
@cindex functions that do not handle memory bank switching on 68HC11/68HC12
