Message undeliverable: Directorio Empresarial Mexico - Edicion 2020.

2020-03-16 Thread mailer-daemon
Your message did not reach some or all of the intended recipients. Sent: 9 Mar 2020 01:38:16 -0600 Subject: Directorio Empresarial Mexico - Edicion 2020. The following recipient(s) could not be reached: gcc@gcc.gnu.org Error Type: SMTP Remote server (8.43.85.97) issued an error. h

Attribute visibility

2020-03-16 Thread Visda.Vokhshoori--- via Gcc
Hello, In configuring gcc, there's a check to determine if the linker has support for STV_Hidden. It determines support by checking for the date in the linker's version string. On the other hand, the version string for the linker is constructed without a date, bfd/Makefile.am recipe for bfdve

Mrb .....

2020-03-16 Thread Siparis/Muhasebe via Gcc
Bu mesajın metin bölümüdür. Eski tip email müşteri kullanıcıları için gösterilir.

Re: Fw: GSoC topic: Implement hot cold splitting at GIMPLE IR level

2020-03-16 Thread Jakub Jelinek via Gcc
On Mon, Mar 16, 2020 at 11:11:14PM +, Aditya K via Gcc wrote: > > > > 2) ipa-split is very simplistic and only splits when there is no value > >computed in header of function used in the tail. We should support > > adding extra parameters for values computed and do more general SESE > >

Re: Fw: GSoC topic: Implement hot cold splitting at GIMPLE IR level

2020-03-16 Thread Aditya K via Gcc
> > 2) ipa-split is very simplistic and only splits when there is no value >computed in header of function used in the tail. We should support > adding extra parameters for values computed and do more general SESE >outlining > Note that we do SESE outlining for openMP but this code is

Integrating GCC with oss-fuzz

2020-03-16 Thread David Korczynski
Hi! My name is David Korczynski and I have been doing some work on integrating fuzzing by way of OSS-Fuzz into the gcc project. This came out of fuzzing libiberty within the binutils project where we found several bugs within libiberty. However, the binutils owners are not working on libiberty

Compilation speed notes

2020-03-16 Thread Paul Smith
Hi all; thanks for the help recently with sysroot compilers. I was able to get things building following advice from Joseph and Jonathan. I did want to mention that I noticed that GCC got non-trivially slower between my previous version (8.1) and this new version (9.3). I have a decently-sized C

Re: Not usable email content encoding

2020-03-16 Thread Jonathan Wakely via Gcc
On Mon, 16 Mar 2020 at 14:13, Martin Liška wrote: > > On 3/16/20 2:54 PM, Alexander Monakov wrote: > > Are you trying to copy from the raw message representation? > > Exactly. That's never been reliable.

Re: Not usable email content encoding

2020-03-16 Thread Martin Liška
On 3/16/20 2:54 PM, Alexander Monakov wrote: Are you trying to copy from the raw message representation? Exactly. Martin

Re: Not usable email content encoding

2020-03-16 Thread Alexander Monakov via Gcc
On Mon, 16 Mar 2020, Martin Liška wrote: > It's probably related to the following email tag: > Content-Transfer-Encoding: quoted-printable > > The format is problematic when copying a patch. > Email example: > https://gcc.gnu.org/pipermail/gcc-patches/2020-March/542053.html I'm surprised it's an

Re: Not usable email content encoding

2020-03-16 Thread Florian Weimer
* Martin Liška: > It's probably related to the following email tag: > Content-Transfer-Encoding: quoted-printable > > The format is problematic when copying a patch. > Email example: > https://gcc.gnu.org/pipermail/gcc-patches/2020-March/542053.html This is a known issue in the redhat.com email i

Re: Not usable email content encoding

2020-03-16 Thread Frank Ch. Eigler via Gcc
Hi - > I noticed some emails reaching gcc-patc...@gcc.gnu.org use the following > quoting: > It's probably related to the following email tag: > Content-Transfer-Encoding: quoted-printable This is not something that the mailing list system does. This content-transfer-encoding comes from the ori

Re: Not usable email content encoding

2020-03-16 Thread Martin Liška
On 3/16/20 2:47 PM, Richard Earnshaw wrote: This isn't new.  It's usually the sender that controls that, though it's often  automatic in their email client. Jakub told me that he sees: Ten mail byl: Content-Type: text/plain; charset=us-ascii Content-Disposition: inline while the email reachin

Re: Not usable email content encoding

2020-03-16 Thread Richard Earnshaw
On 16/03/2020 13:45, Martin Liška wrote: Hello. I noticed some emails reaching gcc-patc...@gcc.gnu.org use the following quoting: ``` case UNGT_EXPR: case UNGE_EXPR: case UNEQ_EXPR: +    case MEM_REF:    /* Binary operations evaluating both arguments (increment and  =0

Not usable email content encoding

2020-03-16 Thread Martin Liška
Hello. I noticed some emails reaching gcc-patc...@gcc.gnu.org use the following quoting: ``` case UNGT_EXPR: case UNGE_EXPR: case UNEQ_EXPR: +case MEM_REF: /* Binary operations evaluating both arguments (increment and =09 decrement are binary internally in GCC). */

Re: GSOC

2020-03-16 Thread Giuliano Belinassi via Gcc
Hi, Shivan. On 03/15, shivam tiwari via Gcc wrote: > In Which Format I have to Send Gsoc Proposal On this Mail PDF or DOC Format Perhaps the best way to write your proposal is to write LaTeX, and then convert it to Markdown using pandoc, and attach it to the mailing list. One example of this appr

Re: [GSoC 2020] Automatic Detection of Parallel Compilation Viability

2020-03-16 Thread Richard Biener
On Fri, 13 Mar 2020, Giuliano Belinassi wrote: > Hi, all > > I want to propose and apply for the following GSoC project: Automatic > Detection of Parallel Compilation Viability. > > Here is the proposal, and I am attaching a pdf file for better > readability: > > **Automatic Detection of Parall

GSOC

2020-03-16 Thread shivam tiwari via Gcc
In the given link I shared My GSOC 2020 Project Proposal And Tell Me If Any Other Extra Point I have to Add on it. Any Give Me feedback About My Project Proposal . https://docs.google.com/document/d/1J2lCtkDPoU0gwp5zk8Ygy0Vg82fNn-ZH0gsv5dBkKok/edit?usp=sharing