From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) by sourceware.org (Postfix) with ESMTPS id 65A2C3858C2C for ; Tue, 4 Jan 2022 21:09:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 65A2C3858C2C Received: by mail-wr1-x429.google.com with SMTP id d9so78766133wrb.0 for ; Tue, 04 Jan 2022 13:09:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BILA9Y3n+gsMN9MT1TEUwjarrHWOY69/+Buq/1Imtrw=; b=GyfljFw+KwB9N0sQj2poCUPOWqv8yhJldfQLLL3keyVeId1SvFVVRRt0UKRQRWUuzN YuDa5HnDs332oXgPRQx138SRymPAt8LcMU5z24XWUNkSxpu5HNy87BjD9jW0xRPIZ/3h VEFGCJRYWqb9JbteOs2AqLMY0Mgr1dsH5LWcXrkjVLUwF7K6ndxVJZudXiCsEnSsLHll ICwyZpzNd2hRaE37xmg5bULx/bLY2jjiyWLTjb2Y2oxlTrzx+2C82+yvjgR2kvH5DaqV 6rghu0OQowsCa/dy96ztGq11gygaPD7+2s0zq4/+lN8zfFcYEatiSRFhXsquh23daS6P g90Q== X-Gm-Message-State: AOAM531kwbuEIuvBcs9ixaQJ5fECy5gYzSK6fzFm/23+UWMDOabRPXd5 +nvWurbwKSh4/9r6BCdEu0s9N97pIoeeVIOEvzM= X-Google-Smtp-Source: ABdhPJyFrU2e71KpOvwiwaX6HtZU6HlKQr19M0xR0FI/WKuQhaaSFDK1jh7rEjHa81/e3SPWBROiCDoN1nEJSS7m+6M= X-Received: by 2002:adf:ec85:: with SMTP id z5mr43994203wrn.568.1641330581433; Tue, 04 Jan 2022 13:09:41 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Jonathan Wakely Date: Tue, 4 Jan 2022 21:09:28 +0000 Message-ID: Subject: Re: Interpreting -fmem-report To: Tom Kacvinsky Cc: gcc-help X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gcc-help@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-help mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2022 21:09:43 -0000 On Tue, 4 Jan 2022, 20:10 Tom Kacvinsky via Gcc-help, wrote: > Hi all, > > I am interested in -fmem-report to help diagnose an issue > with memory thrashing during a parallel build. Ech separate > compilation if and of itself is not enough to cause the thrash, > but when they're added up over a parallel compile, things go > south. > > So I want to collect total memory usage of GCC during a > compilation and then sum them over the last 16 or so GCC > invocations we have. But I am having a hard time figuring > out the total usage. I see nothing obvious. Any hints? > -ftime-report gives a simple total.