| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | xfs: compiler implementation dependent behavior? |
| From: | Joe Perches <joe@xxxxxxxxxxx> |
| Date: | Fri, 15 Apr 2016 12:09:00 -0700 |
| Cc: | xfs@xxxxxxxxxxx, LKML <linux-kernel@xxxxxxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
The value stored in *cycle in xlog_crack_grant_head_val
in xfs_log_priv.h is compiler implementation dependent.
Does it matter?
static inline void
xlog_crack_grant_head_val(int64_t val, int *cycle, int *space)
{
*cycle = val >> 32;
*space = val & 0xffffffff;
}
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 41/42] block: do not use REQ_FLUSH for tracking flush support, Mike Christie |
|---|---|
| Next by Date: | Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io, Toshi Kani |
| Previous by Thread: | [PATCH v2] xfs: buffer ->bi_end_io function requires irq-safe lock, Brian Foster |
| Next by Thread: | [PATCH 00/42] v7: separate operations from flags in the bio/request structs, mchristi |
| Indexes: | [Date] [Thread] [Top] [All Lists] |