block reordering at GIMPLE level?
Hello, While working on our CLI port, I realized that we were missing, among others, the block reordering pass. This is because we emit CLI code before the RTL passes are reached. Looking at the backend optimizations, it is clear that some modify the CFG. But my understanding is that loop optimizations and unrolling are also being moved to GIMPLE. I do not know about others. Could it be that sometime all the optimizations that modify the CFG are run on GIMPLE? Is there any plan/interest in having a block layout pass running at GIMPLE level? Cheers, -- Erven.
mismatch in parameter of builtin_ffs?
Hello, Looking at builtins, I think I have found something inconsistent. __builtin_ffs is defined in the documentation as taking an unsigned int parameter: Built-in Function: int __builtin_ffs (unsigned int x) However in the file builtins.def, it is defined as: DEF_EXT_LIB_BUILTIN (BUILT_IN_FFS, "ffs", BT_FN_INT_INT, ATTR_CONST_NOTHROW_LIST) that is: it takes an int. I think it should be BT_FN_INT_UINT. (Other functions like clz, parity, popcount are defined with unsigned int.) Unless I am missing something... -- Erven.
GROW 2011: deadline extended to 7 February 2011
The submission deadline for the 3rd Workshop on GCC Opportunities has been extended until 7 February 2011. CALL FOR PAPERS 3rd Workshop on GCC Research Opportunities (GROW 2011) http://grow2011.inria.fr 3 April 2011, Chamonix, France (co-located with CGO 2011) The GROW workshop focuses on current challenges in research and development of compiler analyses and optimizations based on the free GNU Compiler Collection (GCC). The goal of this workshop is to bring together people from industry and academia that are interested in conducting research based on GCC and enhancing this compiler suite for research needs. The workshop will promote and disseminate compiler research (recent, ongoing or planned) with GCC, as a robust industrial-strength vehicle that supports free and collaborative research. The program will include an invited talk and a discussion panel on future research and development directions of GCC. Topics of interest Any issue related to innovative program analysis, optimizations and run-time adaptation with GCC including but not limited to: * Classical compiler analyses, transformations and optimizations * Power-aware analyses and optimizations * Language/Compiler/HW cooperation * Optimizing compilation tools for heterogeneous/reconfigurable/ multicore systems * Tools to improve compiler configurability and retargetability * Profiling, program instrumentation and dynamic analysis * Iterative and collective feedback-directed optimization * Case studies and performance evaluations * Techniques and tools to improve usability and quality of GCC * Plugins to enhance research capabilities of GCC Paper Submission Guidelines Submitted papers should be original and not published or submitted for publication elsewhere; papers similar to published or submitted work must include an explicit explanation. Papers should use the LNCS format and should be 12 pages maximum. Papers will be refereed by the Program Committee and if accepted, and if the authors wish, will be made available on the workshop web site. Important Dates Deadline for submission: 31 January 2011 --> EXTENDED 7 February Decision notification: 28 February 2011 Workshop: 3 April 2011 full-day Organizers David Edelsohn, IBM, USA Erven Rohou, INRIA, France Program Committee Zbigniew Chamski, Infrasoft IT Solutions, Poland Albert Cohen, INRIA, France David Edelsohn, IBM, USA Björn Franke, University of Edinburgh, UK Grigori Fursin, EXATEC Lab, France Benedict Gaster, AMD, USA Jan Hubicka, SUSE Paul H.J. Kelly, Imperial College of London, UK Ondrej Lhotak, University of Waterloo, Canada Hans-Peter Nilsson, Axis Communications, Sweden Diego Novillo, Google, Canada Dorit Nuzman, IBM, Israel Andrea Ornstein, STMicroelectronics, Italy Sebastian Pop, AMD, USA Erven Rohou, INRIA, France Ian Lance Taylor, Google, USA Chengyong Wu, ICT, China Kenneth Zadeck, NaturalBridge, USA Ayal Zaks, IBM, Israel
Re: Source code of CIL back-end
Joe Buck wrote: On Thu, Jun 22, 2006 at 11:49:45AM +0200, Roberto COSTA wrote: By the way, is there any news about the status of the CIL issue? I'm sorry to bother the list readers about this, but whom could I directly ask? Sorry for the delay in answering, Robert. I was out of town, and apparently people thought I'd post the answer on this one, since I brought up the topic for SC discussion. The SC discussed it with Richard Stallman, and he agrees that it is not "dangerous" (the FSF had raised objections to byte-code systems in the past, so many of us assumed there would be a problem). So there is no political/legal objection to including a CIL back end. If it passes technical review, it can be included. Hello, Thanks for the answer, this is great news! We have to start working on the paperwork. Could anybody point us at the relevant forms for the copyright assignment? My understanding is that the next step is the creation of a development branch. Is it dependent on the paperwork, or can it be done in parallel? Thanks, -- Erven.
Re: Source code of CIL back-end
Paolo Bonzini wrote: The SC discussed it with Richard Stallman, and he agrees that it is not "dangerous" (the FSF had raised objections to byte-code systems in the past, so many of us assumed there would be a problem). So there is no political/legal objection to including a CIL back end. If it passes technical review, it can be included. Hello, Thanks for the answer, this is great news! It is indeed. It's good to see GCC moving forward on these aspects! We have to start working on the paperwork. Could anybody point us at the relevant forms for the copyright assignment? I am almost sure that you do not need that, because ST Microelectronics has an assignment for many projects including GCC. But just in case, please wait for a confirmation. If you want to assign copyright personally to FSF, it would mean that you could keep working on GCC (in the FSF repository) even if you leave ST. If that is the case, just ask for the relevant forms. My understanding is that the next step is the creation of a development branch. Is it dependent on the paperwork, or can it be done in parallel? It is dependent on the paperwork. However, as I said, I am almost sure that your employer took care of that for you. As soon as somebody confirms that no further paperwork is necessary, you can create the branch. Paolo It turns out that Paolo was right. The Copyright clerk confirmed to me that ST already has the following assignment on file: GCC STMicroelectronics 2004-11-02 Assigns past and future changes. Thanks for letting us know. -- Erven.
