Am 17.03.20 um 22:41 schrieb Andreas Schwab:
On Mär 17 2020, Holger Lamm wrote:
No. The order of elements of structures in memory is implementation
defined and not guaranteed to be the order of enumeration in the
definition.
That is not true. The first member is guaranteed to have the same
a
Hi!
On Tue, Mar 17, 2020 at 03:51:58PM -0400, Frank Ch. Eigler via Gcc wrote:
> > > Are you trying to copy from the raw message representation?
> >
> > Everyone trying to work with a patch (instead of just the email) always
> > is working with the raw message. Just patch < mbox or git-am mbox
On Mär 17 2020, Holger Lamm wrote:
> No. The order of elements of structures in memory is implementation
> defined and not guaranteed to be the order of enumeration in the
> definition.
That is not true. The first member is guaranteed to have the same
address as the whole structure, and subseque
Hi,
Am 02.02.20 um 08:44 schrieb aotto:
Hi, the following scenario has a "definition hole" in the "C" language
code example:
-
struct base {
...
};
struct A {
struct base obj;
...
} aObj;
struct B {
struct base obj;
...
} bObj;
void method_base (struct base
Hi, all
I have applied some revews to the project. Please see the new proposal
here:
https://www.ime.usp.br/~belinass/Automatic_Detection_of_Parallel_Compilation_Viability.pdf
**Automatic Detection of Parallel Compilation Viability**
[Giuliano Belinassi]{style="color: darkgreen"}\
Timezone: GMT
Hi, Richi
Thank you for your review!
On 03/16, Richard Biener wrote:
> 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
Hi -
> > Are you trying to copy from the raw message representation?
>
> Everyone trying to work with a patch (instead of just the email) always
> is working with the raw message. Just patch < mbox or git-am mbox
> for example.
>
> https://gcc.gnu.org/contribute.html says
> It is strongly
On Mon, Mar 16, 2020 at 04:54:51PM +0300, Alexander Monakov via Gcc wrote:
> 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:
On Tue, Mar 17, 2020 at 3:33 PM Aditya K via Gcc wrote:
>
> As I understand the openmp outliner is also at the tree level. A region based
> outliner could be reused there. I’m not particular about the outliner being
> specific to ipa-split. A GSoC project can help us get the coding+testing
> do
As I understand the openmp outliner is also at the tree level. A region based
outliner could be reused there. I’m not particular about the outliner being
specific to ipa-split. A GSoC project can help us get the coding+testing done.
Any pass that needs a function splitting at tree level can reu
On Mon, 16 Mar 2020 at 21:15, David Korczynski wrote:
>
> 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 libib
11 matches
Mail list logo
